frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Elevators

https://john.fun/elevators
1087•Jrh0203•14h ago•257 comments

Flint: A Visualization Language for the AI Era

https://microsoft.github.io/flint-chart/
48•vinhnx•2h ago•9 comments

The development pipeline is a production system

https://sundry.jerryorr.com/2026/07/31/development-pipeline-is-a-production-system
42•firefoxd•2h ago•16 comments

How to Exist

https://www.raptitude.com/2026/07/how-to-exist/
100•walterbell•5h ago•49 comments

qm – Multiplayer agent harness for work

https://github.com/yc-software/qm
521•tosh•11h ago•109 comments

Software for One

https://www.ajwaxman.com/writing/software-for-one
69•awaxman11•2d ago•41 comments

What Liberal Arts Education Is for (2024)

https://innig.net/teaching/liberal-arts-manifesto
10•mr_wiglaf•1h ago•6 comments

History remembers two Robert McNamaras

https://indevelopmentmag.com/numbers-man/
6•salonium_•2d ago•0 comments

BMW Spider-Man in-car advertising

https://consumerrights.wiki/w/BMW_Spider-Man_in-car_advertising
142•goplayoutside•2h ago•55 comments

A Week in Matrix

https://piegames.de/dumps/a-week-in-matrix/
26•Kesseki•4h ago•10 comments

Progressive Web Components

https://arielsalminen.com/2026/progressive-web-components/
125•hosteur•19h ago•17 comments

Firefighter arson a long-standing issue – expert

https://www.firerescue1.com/arson-investigation/articles/expert-firefighter-arson-a-long-standing...
26•gurjeet•1h ago•25 comments

June in Servo: real world compat, media queries, SharedWorker, and more

https://servo.org/blog/2026/07/31/june-in-servo/
128•iamnothere•11h ago•39 comments

Getting 25 Gbps Thunderbolt Ethernet on My Mac Studio

https://www.jeffgeerling.com/blog/2026/getting-25g-ethernet-mac-thunderbolt/
167•speckx•13h ago•92 comments

Show HN: I worked on a new browser for 2 years, today it passed Acid 3

https://code.intellios.ai/cwbrowser/
91•coolwulf•7h ago•28 comments

Run Kimi K3 using 29 GB of RAM at 0.50 tok/s

https://github.com/sqliteai/waste
197•marcobambini•15h ago•82 comments

Big Food vs. the People

https://www.lighthousereports.com/investigation/big-food-vs-the-people/
215•jruohonen•13h ago•139 comments

How far can you push the range of Wi-Fi connectivity in an ideal environment?

https://www.phidgets.com/?view=articles&article=LongRangeWifi
34•rzk•3d ago•21 comments

Demystifying DRAM Read Disturbance: RowHammer and RowPress Phenomena

https://arxiv.org/abs/2607.28233
45•Jimmc414•8h ago•21 comments

Tailscale didn't stop the Hugging Face intrusion

https://tailscale.com/blog/hugging-face-intrusion
508•bluehatbrit•10h ago•195 comments

Let's make the worst Htmx

https://zserge.com/posts/worst-htmx-ever/
86•RebelPotato•1d ago•26 comments

Loops (YC W22) Is Hiring a Product Educator

https://www.ycombinator.com/companies/loops/jobs/zqUnwqB-product-educator-technical-content-creator
1•chrisfrantz•8h ago

The most official water costs $120k a gallon

https://signoregalilei.com/2026/07/26/the-most-official-water-costs-120000-a-gallon/
166•surprisetalk•14h ago•137 comments

The Absurdity of Albert Camus

https://www.historytoday.com/archive/portrait-author-historian/absurdity-albert-camus
80•apollinaire•1d ago•47 comments

Attention Decode on AMD MI450 GPUs: A Gluon Kernel Optimization Guide

https://rocm.blogs.amd.com/software-tools-optimization/gluon-attention-decode-mi450/README.html
6•matt_d•4d ago•0 comments

Twenty-five years ago it was cryptography, today it's model weights

https://weeraman.com/because-we-can/
217•aweeraman•3d ago•96 comments

The First Transatlantic Telegraph Cable Was a Bold, Beautiful Failure

https://spectrum.ieee.org/the-first-transatlantic-telegraph-cable-was-a-bold-beautiful-failure
36•sparsesignal•2d ago•11 comments

Golang proposal: container/: generic collection types

https://github.com/golang/go/issues/80590
142•jabits•10h ago•94 comments

Is AI reasoning right for the wrong reasons?

https://www.quantamagazine.org/is-ai-reasoning-right-for-the-wrong-reasons-20260731/
140•retupmoc01•14h ago•166 comments

Authorize, don't authenticate

https://blog.marcua.net/2026/07/31/authorize-dont-authenticate.html
70•marcua•15h ago•24 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.