frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Kimi K3.1 Pro and K3.1 Pro Highspeed

https://www.kimi.ai/blog/kimi-k3-1-pro
837•Jowsey•13h ago•494 comments

Twelve years of distributed SQLite

https://philipotoole.com/twelve-years-of-distributed-sqlite/
119•otoolep•4h ago•13 comments

Apple Music 404 Not Found

https://music.apple.com/this-url-doesnt-exist
699•frizlab•17h ago•215 comments

How close can pure functional programming get to C?

https://rtfeldman.com/fp-vs-c
41•stmonty•2h ago•4 comments

Local Wikipedia: Wikipedia, but only for things a half hour walk from you

https://edjefferson.com/localwiki/
1334•sohkamyung•1d ago•229 comments

Dessa: Conversation Model trained only on speech

https://block.xyz/dessa
334•dsr12•11h ago•128 comments

A practical guide to AI image generation, from diffusion to agents

https://danielball.com/notes/ai_image_generation.html
25•westsmith•3d ago•4 comments

Today, we hacked what we'd set out to hack: the iPhone

https://blog.calif.io/p/iphone
818•pavel_lishin•13h ago•538 comments

CVE Tracker

https://cve.0xosprey.com/
146•Group_B•8h ago•59 comments

Bringing uv and ty together

https://astral.sh/blog/uv-ty-integration
91•Ravencentric•3d ago•23 comments

The Quake Fan who built the map editor everybody uses

https://funcarena.com/articles/the-quake-fan-who-built-the-map-editor-everybody-uses
64•klaussilveira•1d ago•4 comments

One Man's Pan Am 747 Replica [video]

https://www.youtube.com/watch?v=vAFwHGGfPz4
18•Teever•8h ago•1 comments

Canadians are running out of time to oppose Bill C-22

https://www.eff.org/deeplinks/2026/10/canadians-are-running-out-time-oppose-dangerous-c-22-survei...
383•hn_acker•1d ago•206 comments

The Best Monopoly Strategy, Tested on 300M Games [video]

https://www.youtube.com/watch?v=S_2eVAaw1UM
5•zdw•3d ago•2 comments

The Real Kevin Bacon

https://pudding.cool/2026/10/kevin-bacon/
278•xnx•3d ago•76 comments

C vs. C#: racing VLC's Gaussian blur

https://martinfinkel.com/blog/gaussian-blur-c-vs-csharp/
54•martz•3d ago•5 comments

OBS Studio 33

https://github.com/obsproject/obs-studio/releases/tag/33.0.0
3•pentagrama•1h ago•0 comments

The past, present, and future share a show floor at Pinball Expo 2026

https://arstechnica.com/gaming/2026/10/the-past-present-and-future-share-a-show-floor-at-pinball-...
25•civicpivot•2d ago•4 comments

Show HN: Corgi, a helpful {agent, terminal} multiplexer

https://corgi.computer/
65•eiopa•10h ago•16 comments

Air Purifiers as White Noise Machines

https://www.jefftk.com/p/air-purifiers-as-white-noise-machines
103•luu•12h ago•106 comments

How Block Blast harvests its players for ad money

https://ayoships.com/breakdowns/block-blast
12•motionlessveloc•3h ago•2 comments

Rise of collagen-eating microbes may help explain gaps in the fossil record

https://www.cam.ac.uk/research/news/rise-of-collagen-eating-microbes-may-help-explain-gaps-in-the...
29•gmays•3d ago•0 comments

UUIDv7: Timestamps aren’t time-ordered and other oddities

https://alexsci.com/blog/uuidv7-is-weird/
126•ibobev•13h ago•104 comments

Alzheimer's breakthrough: 2 hrs of sleep restored without clearing brain plaques

https://www.sciencedaily.com/releases/2026/10/261018084421.htm
72•amichail•4h ago•20 comments

Evolving Threat: http2shell is an RCE in Node, Python, and more

https://nitter.click/AikidoSecurity/status/2113759110625906950?__galadriel=lPmlGl9id4oAd5UeBwMhlY...
142•cowlevel•6h ago•76 comments

How is music possible

https://www.henrikkarlsson.xyz/p/music
108•rafaelc•13h ago•74 comments

A Bicycle Journey Across Brazil to Find a Vanishing Savanna

https://e360.yale.edu/features/2026-film-contest-second-place-cerrado
40•throwaway2037•2d ago•10 comments

Rune 1.3: adds TypeScript, a Helix editor, Kitty graphics and OSC-7501

https://rune.build/blog/rune-1-3-release
47•ernestrc•10h ago•11 comments

Is this the new cyber normal?

https://drew.silcock.dev/blog/is-this-the-new-cyber-normal/
156•drewsberry•19h ago•185 comments

Animations for System Builders

https://brooker.co.za/blog/2026/10/23/animations.html
54•KraftyOne•13h ago•3 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.