frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

PipePipe: NewPipe hard fork implementing SponsorBlock

https://github.com/InfinityLoop1308/PipePipe
246•Qision•1d ago•130 comments

DeepSeek Elastic Compute (DSec)

https://arxiv.org/abs/2609.22978
50•shenli3514•3h ago•12 comments

Show HN: Reladraw – A diagram language where you decide where to place things

https://github.com/reladraw/reladraw
87•jpwalsh234•4h ago•25 comments

A searchable library of forgotten public-domain film clips from 1915 onward

https://www.movingimagearchive.com/
66•momentmaker•2d ago•13 comments

Drawgent: Coding agent on a live Excalidraw canvas

https://tangled.org/yanndegat.tngl.sh/drawgent
78•parasitid•5h ago•26 comments

Welcome to the Medical Clinic at the Interplanetary Relay Station

https://www.lightspeedmagazine.com/fiction/welcome-to-the-medical-clinic-at-the-interplanetary-re...
10•bucket2015•1h ago•0 comments

Fifteen years later, the Apple Cards origin story

https://lexontech.org/fifteen-years-later-the-apple-cards-origin-story
306•ksec•12h ago•68 comments

The Lost Atomic Update on Loongson CPU

https://jia.je/hardware/2026/09/24/loongson-cpu-erratum-en/
85•jiegec•2d ago•4 comments

Modern Object Pascal Introduction for Programmers

https://castle-engine.io/modern_pascal
121•birdculture•2d ago•43 comments

Revealing the details of how OpenAI agents hacked Hugging Face

https://swarmtraces.org/
686•specked-citrus•1d ago•435 comments

LA Metro has some of the slowest escalators on Earth

https://basin.la/articles/ninety-feet-a-minute.html
14•big_toast•2d ago•7 comments

We're gonna need a lot more mathematicians

https://terrytao.wordpress.com/2026/09/24/were-gonna-need-a-lot-more-mathematicians/
336•srcreigh•18h ago•439 comments

The Rise of Audio AR

https://www.dbreunig.com/2024/04/10/the_rise_of_audio_ar.html
19•dbreunig•2d ago•5 comments

Analyzing Frontier Model Progress with My Favourite Game: Prince of Persia

https://blog.priyan.in/2026/09/analyzing-frontier-model-progress-with.html
46•msephton•1d ago•31 comments

Breaking Up with Google Play: Why Conversations Is Now Free

https://gultsch.de/posts/breaking-up-with-google-play/
600•ezst•10h ago•230 comments

Plan mode is dead

https://www.aymannadeem.com/artificial/intelligence,/developer/tools/2026/09/24/plan-mode-is-dead...
527•jmvldz•1d ago•462 comments

How to keep enjoying programming in a world of LLMs

https://discourse.haskell.org/t/how-to-keep-enjoying-programming-in-a-world-of-llms/14705
113•signa11•11h ago•166 comments

Plunging test scores are a slow-moving catastrophe

https://www.economist.com/leaders/2026/09/10/plunging-test-scores-are-a-slow-moving-catastrophe
141•vinni2•6h ago•260 comments

The Murky History of Soviet-Born Tetris

https://thereader.mitpress.mit.edu/the-bizarre-murky-history-of-soviet-born-tetris/
96•EA-3167•1d ago•26 comments

Ollaya – Ollama for open-source, Jev-style decision models

https://ollaya.dev/
579•Ardakilic•1d ago•139 comments

Reflections on 1,000 Days of Math

https://gmays.com/reflections-on-1000-days-of-math/
71•gmays•3d ago•31 comments

OpenAI bots meddled with multiple US Government agency sites

https://www.bbc.com/news/articles/cw62jje658dlo
81•Betelbuddy•7h ago•111 comments

Automattic has a new board after failed attempt to put CEO on leave

https://techcrunch.com/2026/09/25/automattic-has-a-new-board-after-failed-attempt-to-put-ceo-on-l...
99•ilamont•5h ago•112 comments

Floci: Locally emulating any cloud service

https://floci.io
147•theanonymousone•12h ago•27 comments

Show HN: Jev Plays Pokémon Red

https://jev-pokemon.vercel.app/
251•pancomplex•1d ago•109 comments

Experiencing writing at our recent Chinese calligraphy workshop

https://viewsproject.wordpress.com/2026/09/06/chinese-calligraphy-workshop/
27•surprisetalk•2d ago•1 comments

16GB iPod Nano 3G Upgrade

https://tuckerosman.com/projects/16gb-ipod-nano
134•Ivoah•2d ago•22 comments

What even is an OS now?

https://sockpuppet.org/blog/2026/09/25/what-even-is-an-os-now/
286•fratellobigio•23h ago•433 comments

Is your Postgres migration safe or not safe?

https://safenotsafe.dev/
116•vira28•13h ago•40 comments

Banks and Credit Unions to Team Up Against Apple Pay Fees

https://www.macrumors.com/2026/09/25/apple-pay-antitrust-lawsuit-advances/
97•Brajeshwar•5h ago•78 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.