frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

OpenRouter raises $113M Series B

https://openrouter.ai/announcements/series-b
58•freeCandy•37m ago•10 comments

Zig ELF Linker Improvements Devlog

https://ziglang.org/devlog/2026/#2026-05-30
23•kristoff_it•35m ago•1 comments

Voxel Space

https://s-macke.github.io/VoxelSpace/
155•davikr•3h ago•32 comments

Openrsync: An implementation of rsync, by the OpenBSD team

https://github.com/kristapsdz/openrsync
214•sph•7h ago•94 comments

Pandoc Templates

https://pandoc-templates.org/
289•ankitg12•8h ago•41 comments

Werner Herzog in conversation with Paul Cronin (2014)

https://fsgworkinprogress.com/2014/09/26/insignificant-bullets-evil-poachers-and-l-a-culture/
21•Michelangelo11•1h ago•5 comments

Microcode inside the Intel 8087 floating-point chip: register exchange

https://www.righto.com/2026/05/microcode-inside-intel-8087-floating.html
10•pwg•37m ago•1 comments

Navier-Stokes fluid simulation explained with Godot game engine

https://myzopotamia.dev/navier-stokes-fluid-simulation-explained-with-godot
109•myzek•3d ago•20 comments

It Takes Two Neurons to Ride a Bicycle

https://fermatslibrary.com/s/it-takes-two-neurons-to-ride-a-bicycle#email-newsletter
48•malshe•4d ago•11 comments

Downdetector and Speedtest sold to Accenture for $1.2B

https://www.theverge.com/tech/889234/downdetector-ookla-speedtest-sold-accenture
58•Garbage•1h ago•24 comments

Zig: Build System Reworked

https://ziglang.org/devlog/2026/#2026-05-26
271•tosh•9h ago•167 comments

IXI's autofocusing lenses are almost ready to replace multifocal glasses

https://www.engadget.com/wearables/ixis-autofocusing-lenses-multifocal-glasses-ces-2026-212608427...
104•amichail•2d ago•45 comments

Show HN: Helios – what plug-in solar could generate for any address in Britain

https://helios.southlondonscientific.com/
81•ruaraidh•6h ago•27 comments

What Happened to the Locusts?

https://explosion-scratch.github.io/locusts/
142•explosion-s•4d ago•31 comments

SQLite is all you need for durable workflows

https://obeli.sk/blog/sqlite-is-all-you-need-for-durable-workflows/
638•tomasol•1d ago•341 comments

Testing the WWI concrete ships and WWII concrete barges

https://thecretefleet.com/blog/f/testing-the-wwi-concrete-ships-and-wwii-concrete-barges
28•surprisetalk•1d ago•7 comments

Memory decline after menopause linked to loss of estrogen production in brain

https://news.northwestern.edu/stories/2026/05/memory-decline-after-menopause-linked-to-loss-of-es...
91•gmays•4h ago•38 comments

Stateless Actors

https://www.massicotte.org/stateless-actors/
4•frizlab•1d ago•0 comments

Notes from the Mistral AI Now Summit

https://koenvangilst.nl/lab/mistral-ai-now-summit
434•vnglst•1d ago•185 comments

A Probabilistic Algorithm for Repairing All Roads in Lebanon via Papal Visits

https://sigbovik.org/2026/proceedings.pdf#%5B%7B%22num%22%3A13%2C%22gen%22%3A0%7D%2C%7B%22name%22...
43•kmstout•2h ago•2 comments

MCP is dead?

https://www.quandri.io/engineering-blog/mcp-is-dead
352•nadis•19h ago•335 comments

Snowboard Kids 2 is 100% Decompiled

https://blog.chrislewis.au/snowboard-kids-2-is-100-decompiled/
262•GaggiX•3d ago•99 comments

Macsurf, "modern" web browser for macOS 9

https://github.com/mplsllc/macsurf
82•gattilorenz•11h ago•16 comments

The Last Technical Interview

https://steve-yegge.medium.com/the-last-technical-interview-bc13ddcf4564
203•headalgorithm•22h ago•188 comments

Print with dozens of colors: Our new open-source ColorMix for PrusaSlicer

https://blog.prusa3d.com/our-new-open-source-colormix-model-in-prusaslicer-and-easyprint_136079/
206•rented_mule•3d ago•59 comments

Floor and Ceil versus Denormals on CPU and GPU

https://asawicki.info/news_1802_floor_and_ceil_versus_denormals_on_cpu_and_gpu
40•ibobev•4d ago•15 comments

Ask HN: What Is the State of App Development in 2026?

31•karakoram•2h ago•15 comments

The dead economy theory

https://www.owenmcgrann.com/p/the-dead-economy-theory
1194•WillDaSilva•1d ago•1306 comments

It's hard to justify buying a Framework 12

https://www.jeffgeerling.com/blog/2026/its-hard-to-justify-framework-12/
363•watermelon0•1d ago•579 comments

Shift will clean homes for free to train future robots

https://www.theverge.com/ai-artificial-intelligence/939765/ai-training-data-startup-shift-free-cl...
176•evilsimon•22h ago•237 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.