frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

AWS emulator

https://github.com/aws/aws-emulator
576•super_linear•5h ago•195 comments

Tim Peters has died

https://discuss.python.org/t/in-memoriam-tim-peters-1952-2026/110028
771•ayhanfuat•16h ago•76 comments

93% of Paint Splatters Are Valid Perl Programs (2019)

https://www.mcmillen.dev/sigbovik/
42•zenincognito•1h ago•9 comments

United Airlines bans AI agents from booking flights on behalf of travelers

https://www.cbsnews.com/news/united-airlines-bans-ai-agents-booking-flights/
254•herpderperator•2h ago•236 comments

Lock Your GitHub Actions

https://hugovk.dev/blog/2026/lock-github-actions/
60•gslin•1h ago•12 comments

A false smoke alarm almost drowned Jane Street's only NYC datacenter

https://michael.bacarella.com/2026/11/10/false-smoke-alarm-jane-street-datacenter/
378•mbac32768•7h ago•188 comments

Gemini Decisions API

https://blog.google/innovation-and-ai/technology/developers-tools/gemini-decisions-api/
207•iamdelirium•5h ago•69 comments

Emacs in the Age of Magic

https://commandlinesystems.com/magic.txt
112•ggcr•3h ago•42 comments

Show HN: I recreated Papers Please but you're deciding which YC startups to fund

https://termsheetplease.com/
148•bolau•4h ago•63 comments

Nvidia prepares to fire CEO Jensen Huang, WSJ reports

https://twitter.com/watcherguru/status/2120645607866188008
71•alexmolas•1h ago•12 comments

Huawei releases MACaQ, its internal quantizer for local inference

https://github.com/huawei-csl/MACaQ
43•thefox96•3h ago•17 comments

The Utah Teapot

https://graphics.cs.utah.edu/teapot/
46•cobbal•3h ago•11 comments

Faster Retrieval for Better, More Efficient RAG

https://machinelearning.apple.com/research/faster-retrieval
132•zerop•6h ago•23 comments

Flying on Green: Why Farmers Are Turning to Drones for Cover Crop Seeding

https://www.agweb.com/news/machinery/flying-green-why-farmers-are-turning-drones-cover-crop-seeding
29•rmason•2d ago•21 comments

My AI agents found an unmapped Maya site

https://pietromiotti.com/latest/maya-site
907•eyvindn•11h ago•333 comments

Hyper-Realistic Sand with WebGL2

https://av.github.io/safe-sand/
285•everlier•10h ago•59 comments

A Brief History of Sierra Online (2017)

https://retrofreakreviews.com/2017/01/30/sierra-retrospective/
9•freshtake•1d ago•0 comments

A general purpose Apple Silicon layer for x86-64 PCs

https://github.com/tylertms/Stela
5•iceboundrock•41m ago•2 comments

Show HN: Yogurt – Free, private, open-source alternative to Granola

https://github.com/FrigadeHQ/yogurt
148•brownrout•8h ago•69 comments

Launch HN: Pomerado (YC F26) – Turn any website into an MCP for agents

42•alanjm23•6h ago•35 comments

Optimizing Reference Deletions in Git

https://nayak.im/posts/optimizing-reference-deletion/
12•nayak•3d ago•0 comments

The hardest notes to find on the guitar

https://www.gitori.com/blog/articles/hardest-notes-on-the-guitar-fretboard
45•udit99•7h ago•56 comments

Modern Web Guidance 1.0: The web platform expertise your coding agent is missing

https://developer.chrome.com/blog/modern-web-guidance-v1
5•qainsights•21m ago•0 comments

Atuin Threads: All your agent sessions on every machine

https://blog.atuin.sh/threads-agent-sessions/
182•linsomniac•9h ago•65 comments

IBM Quantum Nighthawk Demonstrates New Levels of Speed and Quality

https://newsroom.ibm.com/2026-11-11-ibm-quantum-nighthawk-demonstrates-new-levels-of-speed-and-qu...
43•gok•3h ago•22 comments

The Apple Support Community will permanently close on November 20, 2026

https://discussions.apple.com/welcome
100•tech234a•20h ago•198 comments

Can a Linear Program Do Weight-Space Programming?

https://nathan.rs/posts/weight-space-lp/
233•emschwartz•11h ago•35 comments

Using voltage glitching to unleash the A100 in my mining card

https://blog.kate.land/posts/using-voltage-glitching-to-unlock-the-a100/
253•lae•12h ago•101 comments

Tinfoil (YC P25) is hiring an applied AI security engineer in San Francisco

1•FrasiertheLion•11h ago

Tools for exploring the souls of large language models

https://oshea00.github.io/posts/tinygpt-visualizer/
26•r00tanon•2h ago•8 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.