frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

JetKVM Mini

https://jetkvm.com/blog/introducing-jetkvm-mini
13•taubek•32m ago•6 comments

Why are AI agents lying, cheating and coordinating?

https://yoshuabengio.org/en/publication/why-are-ai-agents-lying-cheating-and-coordinating
157•jonifico•6h ago•183 comments

The Interim Computer Museum

https://icm.museum/
101•mulmen•5h ago•9 comments

Make your first edit to OpenStreetMap

https://high5apps.github.io/josm-plugin-website-wizard/
439•juliantigler•15h ago•105 comments

I Added a Non-Wi-Fi Mitsubishi AC to Home Assistant

https://medium.com/@ivangomezarnedo/how-i-added-a-non-wi-fi-mitsubishi-ac-to-home-assistant-22770...
61•ichacas•2d ago•29 comments

Aligned to whom?

https://hyperbo.la/w/aligned-to-whom/
34•lopopolo•5h ago•9 comments

Apple iPod Engraver (2019)

https://dunstanorchard.com/apple-ipod-engraver/
199•NaOH•4d ago•51 comments

Nvidia is the central bank of AI

https://www.economist.com/interactive/briefing/2026/09/03/nvidia-is-the-central-bank-of-ai
469•tolugenius•17h ago•330 comments

A succession crisis that tore England apart (2023)

https://www.historytoday.com/archive/feature/succession-crisis-tore-england-apart
28•pepys•5h ago•13 comments

Stabilizing Rust's Never Type

https://lwn.net/SubscriberLink/1091015/d9e48318ed242b41/
181•cjd8•3d ago•51 comments

Everyone should slow down AI development except for me

https://xeiaso.net/notes/2026/everyone-slowdown-but-me/
415•xena•7h ago•248 comments

Don't be the out of touch Kung Fu master

https://twitter.com/ID_AA_Carmack/status/2098443262214230095
106•dsubburam•10h ago•88 comments

AgentsDock: An IDE designed for agentic AI research

https://agentsdock.net/
45•ZihuiGeorgia•8h ago•23 comments

A wandering black hole caught feeding on the run

https://phys.org/news/2026-08-black-hole-caught.html
13•wglb•4h ago•2 comments

P(doom)

https://lucumr.pocoo.org/2026/9/12/pdoom/
70•lumpa•10h ago•38 comments

Vintage Scientific Papers with LaTeX

https://github.com/Foadsf/vintage-latex
58•petalmind•3d ago•6 comments

Durable execution without history replay

https://trigora.dev/blog/durable-execution-without-history-replay/
17•hypervs•3d ago•3 comments

Operation Smart Kettle – Börzels Blog

https://blog.boerzel.de/de/blog/operation-smart-kettle
3•marbartolome•2d ago•1 comments

LG denies TV spying claims, says tracking and snooping concerns 'not true'

https://www.tomshardware.com/tech-industry/big-tech/lg-strongly-denies-tv-security-claims-says-tr...
512•datakan•2d ago•404 comments

Liesegang Rings

https://chillphysicsenjoyer.substack.com/p/liesegang-rings
34•surprisetalk•3d ago•4 comments

Getting 50 GB/S Back from the Apple Neural Engine

https://eiln.github.io/posts/ane-dma.html
134•eiln•3d ago•26 comments

We must pace the frontier

https://darioamodei.com/post/we-must-pace-the-frontier
631•apsec112•18h ago•885 comments

After Math

https://terrytao.wordpress.com/2026/09/12/after-math/
59•throwaway81523•5h ago•40 comments

Why So Many AI Researchers Think the Machines Could Kill Everyone

https://www.wired.com/story/why-so-many-ai-researchers-think-the-machines-could-kill-everyone/
8•joozio•1h ago•3 comments

Will there be a 7G?

https://arxiv.org/abs/2609.01877
97•Betelbuddy•15h ago•157 comments

Real-SWE: Benchmarking AI models on private, real-world, enterprise codebases

https://withspecific.com/benchmarks/real-swe
233•theanonymousone•11h ago•133 comments

I made a build visualizer to understand Bun's compile times

https://lalitm.com/post/buildprof/
125•lalitmaganti•17h ago•23 comments

Microcode in Intel's 8087 floating-point chip: the scale instruction

https://www.righto.com/2026/09/8087-microcode-reverse-engineering-fscale.html
105•pwg•16h ago•33 comments

When anyone can build software, who decides what not to build?

https://architectureintel.com/when-anyone-can-build-software-who-decides-what-not-to-build-ae07fd...
29•younss•2h ago•20 comments

Linux Zoom client proactively reading everything written to X11 clipboard

https://hachyderm.io/@simontatham/117201594980991062
289•encyclopedism•13h ago•88 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.