frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Suspected sabotage causes major Netherlands rail disruption

https://www.bbc.com/news/articles/c8ly49w9g1edo
98•choult•1h ago•67 comments

I can't stop thinking about Papua New Guinea

https://notnottalmud.substack.com/p/why-i-cant-stop-thinking-about-papua
282•networked•5h ago•98 comments

How much of F-Droid is LLM generated?

https://tintotint.eu/whacky-corner/f-droid_slop/
49•_ZeD_•1h ago•30 comments

Alternatives to MinIO for single-node local S3

https://rmoff.net/2026/01/14/alternatives-to-minio-for-single-node-local-s3/
38•rmoff•3h ago•26 comments

iOS 27, iPadOS 27, and macOS 27

https://www.apple.com/newsroom/2026/09/major-updates-for-apples-software-platforms-are-now-availa...
625•throw0101d•17h ago•718 comments

OpenArm: An open-source 7DOF humanoid arm

https://github.com/enactic/OpenArm
110•Lwrless•1d ago•21 comments

4,400-Year-Old Tomb of Egyptian Judge Found at Saqqara with Colors on Walls

https://arkeonews.net/4400-year-old-tomb-of-an-egyptian-judge-found-at-saqqara-with-colors-still-...
153•arunbahl•2d ago•50 comments

Pion, an agent designed to run any company autonomously

https://andonlabs.com/blog/why-we-built-pion
419•lukaspetersson•18h ago•519 comments

Linux from Scratch

https://www.linuxfromscratch.org/
209•sippingabonedry•7h ago•69 comments

XCancel service is suspended until further notice

https://xcancel.com/#
658•gaganyaan•1d ago•947 comments

Charts built for Chat

https://dbtcharts.com/blog/charts-built-for-chat/
239•thingsilearned•14h ago•74 comments

CSS-Tricks in Limbo

https://vale.rocks/micros/20260915-0135
22•edent•3h ago•2 comments

The k-server conjecture is true

https://arxiv.org/abs/2609.15979
17•iamsyr•3h ago•8 comments

Lingo.dev (YC F24) is hiring a senior content engineer (Remote, worldwide)

https://lingo.dev/en/careers/ff88132a-cb79-4d35-a6a0-a6230de7a013
1•maxpr•4h ago

Show HN: Redis City – Explore how Redis works in an interactive 3D model

https://poltora.dev/redis
107•poltora•2d ago•19 comments

Dropping eBPF CPU Cost by About 90% with Memoization (Not AI Gen)

https://nathannaveen.dev/posts/dropping-ebpf-cpu-cost-by-90/
127•nathannaveen•20h ago•28 comments

OpenAI bots knew about the RubyGems caching vulnerability

https://tenderlovemaking.com/2026/09/11/what-a-time-to-be-alive/
471•gregnavis•22h ago•380 comments

A beginning for mathematics

https://www.daniellitt.com/blog/2026/9/13/a-beginning-for-mathematics/
233•robinhouston•19h ago•128 comments

Distributed Systems Classics (2017)

https://nvartolomei.com/dist-sys-classics/
313•grep_it•19h ago•68 comments

Let's make quality the norm again

https://www.forbrukerradet.no/short-life/
74•ingve•1h ago•79 comments

Compressing a flag to 11 bits

https://read.vantezzen.io/miniflags
157•bennett_dev•2d ago•61 comments

High-performance garbage collection for C++

https://v8.dev/blog/high-performance-cpp-gc
50•motownphilly•23h ago•9 comments

A rough guide for going back to the Moon

https://research.ibm.com/blog/nasa-ibm-lunar-foundation-model
3•gmays•20h ago•0 comments

Forgotten Woodlands

https://storymaps.arcgis.com/stories/9b790daf22ba4e87836f467abb1c7e49
69•NaOH•3d ago•23 comments

Ubuntu 26.10 completes transition to Rust-based coreutils

https://www.omgubuntu.co.uk/2026/09/ubuntu-2610-rust-coreutils-complete
207•theanonymousone•21h ago•217 comments

Ask HN: What are you working on? (September 2026)

338•david927•1d ago•1051 comments

Show HN: Macros with a Behringer FCB1010 MIDI Pedalboard in macOS

https://github.com/JamesRyanATX/fcbnerd
78•fretlessjazz•12h ago•19 comments

Principles for Fast Tokio Applications

https://dial9-rs.github.io/blog/principles-for-fast-tokio-applications/
220•carllerche•19h ago•53 comments

People who can't picture anything are rewriting the science of imagination

https://dailyneuron.com/aphantasia-mental-imagery-brain-network/
179•giuliomagnifico•22h ago•253 comments

Glyph Immersive

https://glyph.kateander.com/
10•ikers•3d 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.