frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Tell HN: Bob Cringely has died

307•paveworld•4h ago•55 comments

Why don't more developers "use the platform"?

https://nolanlawson.com/2026/10/03/why-dont-more-developers-use-the-platform/
45•vinhnx•1h ago•22 comments

So you think you could be an electrician?

https://asteriskmag.com/issues/15/so-you-think-you-could-be-an-electrician
119•zdw•3d ago•60 comments

We're going to need default hard budget caps on pretty much everything

https://simonwillison.net/2026/Oct/3/default-hard-budget-caps/
335•elffjs•5h ago•169 comments

The work by Valve's Timur Kristóf on improving old AMD GPUs on Linux

https://www.phoronix.com/news/XDC-2026-Valve-Timur-AMDGPU
205•speckx•10h ago•24 comments

Treachery in the Rodin Museum 3D scan verdict

https://cosmowenman.substack.com/p/rodin-museum-3d-scan-verdict
137•CosmoWenman•11h ago•69 comments

Hole Punch: Sling your spaceship around gravitational fields

https://notoriousbfg.com/hole-punch/
265•trwhite•11h ago•62 comments

Agents don't need memory, they need documentation

https://liao.gg/blog/agents-dont-need-memory
115•kmeh•12h ago•64 comments

Celebrating the 100th birthday of the kidney donated to him as a teenager

https://www.whec.com/top-news/webster-man-celebrating-the-100th-birthday-of-the-kidney-his-mom-do...
174•gscott•2d ago•42 comments

Kolibri: A Sovereign Open-Weight Model

https://aleph-alpha.com/en/blog/kolibri-has-landed-a-sovereign-open-weight-model/
561•bastitx•20h ago•311 comments

Reasons I didn't become an EMT, ranked

https://ben.stolovitz.com/posts/reasons-not-emt-ranked/
129•citelao•8h ago•64 comments

Three AI agents, two countries, and one uneven world wide web

https://royapakzad.substack.com/p/multilingual-ai-agents
20•effects•1d ago•0 comments

Math's pedagogical curse – Grant Sanderson [video]

https://www.youtube.com/watch?v=UOuxo6SA8Uc
25•bobajeff•1d ago•8 comments

Your body of work thinks back at you

https://photoni.st/index.php/2026/09/25/your-body-of-work-thinks-back-at-you/
40•surprisetalk•3d ago•1 comments

The characters of plastics (2024)

https://yarchive.net/blog/plastics/
16•thelastgallon•23h ago•2 comments

FTL: A new operating system for clouds

https://ftl-os.org/
161•romac•14h ago•65 comments

We're working on a new RuneScape MMO

https://play.runescape.com/4
15•droidjj•4h ago•5 comments

I quit OpenAI because its culture is broken

https://www.theatlantic.com/technology/2026/10/openai-safety-team-resignation/688881/?gift=v5U_Uz...
139•Brajeshwar•16h ago•406 comments

Show HN: Thoreau BASIC – What if BASIC hadn't gone out of fashion?

https://thoreaubasic.com/
44•Gorsefound•22h ago•13 comments

Former SR-71 engineer talks NASA's Blackbird revival program

https://www.twz.com/air/former-sr-71-engineer-talks-nasas-blackbird-revival-program
35•rkagerer•22h ago•13 comments

Surely you have ultra-wideband radios on your bins too?

https://sjg.io/writing/binrange-have-you-actually-put-the-bins-out/
62•simonjgreen•9h ago•30 comments

Show HN: Pi pod – Run your pi coding agent in sandboxes on your own server

https://pipod.dev/
86•edverma2•1d ago•31 comments

Woking Electrical Control Room (2016)

http://www.darbiansphotography.com/woking-electrical-control-room-urbex
134•NaOH•1d ago•26 comments

Memory-Safe WebP Decoding

https://halide.cx/blog/wpd/
52•computerbuster•1d ago•18 comments

New York City should carefully measure a new tree

https://blog.willmeye.rs/new-york-city-should-carefully-measure-a-new-tree/
66•willmeyers•1d ago•13 comments

C++ Insights – See your source code with the eyes of a Compiler

https://github.com/andreasfertig/cppinsights
151•rramadass•2d ago•28 comments

Federal judge calls Flock 'indiscriminate mass surveillance'

https://techcrunch.com/2026/10/03/federal-judge-calls-flock-indiscriminate-mass-surveillance/
394•sbulaev•7h ago•223 comments

Docker has always used microVMs (well since 2016)

https://dave.recoil.org/docker-has-always-used-microvms/
30•avsm•13h ago•22 comments

RSS Feed Best Practices (2022)

https://kevincox.ca/2022/05/06/rss-feed-best-practices/
49•KomoD•10h ago•9 comments

The Softmax function and its derivative

https://eli.thegreenplace.net/2016/the-softmax-function-and-its-derivative/
25•costco•2d ago•1 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.