frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Ten advances in mathematics and theoretical computer science

https://openai.com/index/ten-advances-in-mathematics/
249•milkshakes•3h ago•509 comments

Devtools must be open source

https://blog.exe.dev/devtools-must-be-open-source
384•bryanmikaelian•6h ago•139 comments

Wind and solar overtake fossil fuels in Germany for the first time

https://www.intellinews.com/wind-and-solar-overtake-fossil-fuels-in-germany-for-the-first-time-ev...
286•just_some_user•7h ago•195 comments

Celebrating 45 Years of Kermit with the First New C-Kermit Release in 15 Years

https://changelog.complete.org/archives/44456-celebrating-45-years-of-kermit-with-the-first-new-c...
82•roryirvine•3h ago•27 comments

Smaller, faster, safer: running Kimi and GLM at scale

https://blog.cloudflare.com/smaller-faster-safer-models/
56•ascorbic•3h ago•10 comments

DDoS against Norwegian government IT infrastructure – status

https://status.digdir.no/incidents/d7hvqmf2yr3l
6•e12e•26m ago•0 comments

MiniMax H3 Day-0 Support in ComfyUI: Open Weights, Native Audio, and 2K Video

https://blog.comfy.org/p/minimax-h3-day-0-support-in-comfyui
207•vblanco•6h ago•59 comments

Andy Pavlo joins ClickHouse to establish ClickHouse Labs

https://clickhouse.com/blog/andy-pavlo-joins-clickhouse
207•nikolay_sivko•6h ago•46 comments

Massively Parallel Postgres Backups

https://planetscale.com/blog/massively-parallel-postgres-backups
58•ksec•3d ago•3 comments

How Hollywood stopped making movies in Hollywood

https://www.statsignificant.com/p/how-hollywood-stopped-making-movies
134•speckx•6d ago•131 comments

200 Milliseconds

https://200ms.thenodebook.com
24•dimitarpanov•2d ago•4 comments

Launch HN: Hoplite (YC S26) – Effortlessly deploy cloud coding agents

https://hoplite.sh
30•BenceRed•3h ago•39 comments

The Billable Usage API: programmatic cost visibility for Cloudflare

https://blog.cloudflare.com/billable-usage-api/
25•ashleypeacock•3h ago•5 comments

Kelly Criterion Simulator

https://kellysimulator.com/
20•aleyan•3d ago•4 comments

AirLLM 70B inference with single 4GB GPU

https://github.com/lyogavin/airllm
158•Anon84•9h ago•61 comments

Use Task Runners for Common Coding Tasks

https://hamvocke.com/blog/task-runners/
35•speckx•3h ago•10 comments

Bonsai: Janestreet's UI Library

https://github.com/janestreet/bonsai
257•KolmogorovComp•11h ago•99 comments

SearXNG in Rust

https://github.com/MikeLuu99/searxng-rust
37•dluuuu•3h ago•17 comments

The Dunning-Kruger Effect Is Probably Not Real

https://www.mcgill.ca/oss/article/critical-thinking/dunning-kruger-effect-probably-not-real
5•audreyfei•43m ago•0 comments

ZX Spectrum System Tour: Sound

https://bumbershootsoft.wordpress.com/2026/08/01/zx-spectrum-system-tour-sound/
8•ibobev•1h ago•0 comments

Don't be a meat proxy

https://gruhn.me/blog/2026-08-03/
1588•ngruhn•13h ago•652 comments

Show HN: Product analytics (and evals) for agent sessions on your MCP

https://armature.tech/
26•screm•4h ago•1 comments

SQLite Critical CVEs or LLM Slop?

https://research.jfrog.com/post/sqlite-critical-cves-or-llm-slops/
676•ymir_e•8h ago•320 comments

SPF Record Syntax: Mechanisms, Qualifiers, Modifiers, and Macros

https://dmarcguard.io/blog/spf-record-syntax/
41•meysamazad•6h ago•10 comments

Prevent cognitive debt by manually retyping LLM-generated code

https://ankursethi.com/blog/prevent-cognitive-debt-by-manually-retyping-llm-generated-code/
324•mpweiher•10h ago•271 comments

C++ float-to-int conversion can be undefined behavior

https://kttnr.net/blog/cpp-float-to-int-conversion-undefined-behavior/
35•signa11•4d ago•34 comments

Explanation of INT8 ConvRot (FP8 is no longer needed)

https://note.com/hirorohi03/n/n047a8c5f7f8b?hl=en
17•peter_d_sherman•4h ago•6 comments

Rust project goals: Immobile types and guaranteed destructors

https://github.com/rust-lang/rust-project-goals/blob/main/src/2026/move-trait.md
210•paavohtl•13h ago•83 comments

Qwen3.8-Max: A New Bar for Coding and Cowork

https://qwen.ai/blog?id=qwen3.8
1007•ai2027•18h ago•537 comments

What DMARC Protects You From, and What It Does Not

https://senderledger.com/articles/what-dmarc-actually-protects-you-from
117•adulion•10h ago•29 comments
Open in hackernews

The Fastest Way yet to Color Graphs

https://www.quantamagazine.org/the-fastest-way-yet-to-color-graphs-20250512/
62•GavCo•1y ago

Comments

tonyarkles•1y ago
In case you haven't looked at the article, this is looking specifically at the Edge Coloring problem and not the more commonly known Vertex Coloring problem. Vertex Coloring is NP-complete unfortunately.
erikvanoosten•1y ago
You can convert edge coloring problems into vertex coloring problems and vice versa through a simple O(n) procedure.
meindnoch•1y ago
Wrong. You can convert edge-coloring problems into vertex-coloring problems of the so-called line graph: https://en.m.wikipedia.org/wiki/Line_graph

But the opposite is not true, because not every graph is a line graph of some other graph.

erikvanoosten•1y ago
Indeed. Thanks, I stand corrected.
tonyarkles•1y ago
Hrm... right. It's been a while. And it looks like both Vertex Coloring and Edge Coloring are both NP-complete (because of the O(n) procedure you're talking about and the ability to reduce both problems down to 3-SAT). I've started looking closer at the actual paper to try to figure out what's going on here. Thanks for the reminder, I miss getting to regularly work on this stuff.

Edit: thanks sibling reply for pointing out that it's not a bidirectional transform.

mauricioc•1y ago
For the edge-coloring problem, the optimal number of colors needed to properly color the edges of G is always either Delta(G) (the maximum degree of G) or Delta(G) + 1, but deciding which one is the true optimum is an NP-complete problem.

Nevertheless, you can always properly edge-color a graph with Delta(G) + 1 colors. Finding such a coloring could in principle be slow, though: the original proof that Delta(G) + 1 colors is always doable amounted to a O(e(G) * v(G)) algorithm, where e(G) and v(G) denote the number of edges and vertices of G, respectively. This is polynomial, but nowhere near linear. What the paper in question shows is how, given any graph G, to find an edge coloring using Delta(G) + 1 colors in O(e(G) * log(Delta(G))) time, which is linear time if the maximum degree is a constant.

Syzygies•1y ago
Yes. The article ran through this point as follows:

"In 1964, a mathematician named Vadim Vizing proved a shocking result: No matter how large a graph is, it’s easy to figure out how many colors you’ll need to color it. Simply look for the maximum number of lines (or edges) connected to a single point (or vertex), and add 1."

I keep wondering why I ever read Quanta Magazine. It takes a pretty generous reading of "need" to make this a correct statement.

JohnKemeny•1y ago
phkahler•1y ago
Is this going to lead to faster compile times? Faster register allocation...
john-h-k•1y ago
Very few compilers actually use vertex coloring for register allocation
isaacimagine•1y ago
Totally. The hard part isn't coloring (you can use simple heuristics to get a decent register assignment), rather, it's figuring out which registers to spill (don't spill registers in hot loops! and a million other things!).
NooneAtAll3•1y ago
and this post isn't even about vertex coloring
DannyBee•1y ago
No.

In SSA, the graphs are chordal, so were already easily colorable (relatively).

Outside of SSA, this is not true, but the coloring is still not the hard part, it's the easy part.

Not really. Coloring a graph is almost always talking about proper coloring, meaning that things that objects that are related receive different colors.

If you read the introduction, you'll also read that the goal is to "color each of your lines and require that for every point, no two lines connected to it have the same color."

Ps. "How many colors a graph needs" is a very well established term in computer science and graph theory.

mockerell•1y ago
I think the comment referred to the phrase „a graph needs X (colors or whatever)“. For me, this can be read two ways: 1. „a graph always needs at least X colors“ or 2. „a graph always needs at most X colors“.

Personally, I would interpret this as option 1 (and so did the comment above I assume). In that case, the statement is wrong. But I’d prefer to specify „at most/ at least“ anyways.

Or even better, use actual vocabulary. „For every graph there exists a coloring with X colors.“ or „any graph can be coloured using X colors“.

PS: I also agree with the sentiment about quanta magazine. It’s hard to get some actual information from their articles if you know the topic.

JohnKemeny•1y ago
What about this statement:

No matter how large a car is, it is easy to figure out how much money you'll need to buy it. Simply look at the price tag.

(From: No matter how large a graph is, it’s easy to figure out how many colors you’ll need to color it. Simply look for the maximum ...)

mauricioc•1y ago
Parent's point is that sometimes (but not always) the store is perfectly fine selling you a car for $1 less than what the "price tag" of Delta(G)+1 dollars asks for, so "need" is a bit inaccurate.