frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

“I just chose words carefully”

https://unsung.aresluna.org/i-just-chose-words-carefully/
667•zdw•9h ago•162 comments

P99 0 ms* autocomplete for 240M domain names

https://ruurtjan.com/articles/p99-0ms-autocomplete-for-240-million-domain-names
78•dbalatero•4h ago•34 comments

Creepy Crawlies

https://people.kernel.org/monsieuricon/creepy-crawlies
1089•zdw•1d ago•533 comments

Transfer files over an Ethernet patch cable

https://maurycyz.com/misc/etherfiles/
58•jllyhill•4h ago•39 comments

My hobby of building miniatures and taking pretty pictures

https://sandyuraz.com/blogs/tiny-cafe/
80•thecsw•2d ago•12 comments

It takes 5 cloud services to hear my doorbell

https://blog.vghaisas.com/rube-goldberg-doorbell/
127•vghaisas•2d ago•101 comments

Matrox: Graphics for Professionals

https://www.abortretry.fail/p/matrox
88•BirAdam•8h ago•27 comments

Highlighting My Code Based on How Much I Care

https://hank.bond/posts/highlighting-my-code-based-on-how-much-i-care/
18•hankbond•2d ago•4 comments

A 12TB Steam "teraleak" spills more than a decade of lost PC gaming history

https://arstechnica.com/gaming/2026/08/a-12tb-steam-teraleak-spills-more-than-a-decade-of-lost-pc...
42•WithinReason•1h ago•3 comments

Understanding ChatGPT Work

https://simonwillison.net/2026/Aug/30/understanding-chatgpt-work/
149•gmays•6h ago•50 comments

Haiku R1/beta6 has been released

https://www.haiku-os.org/news/2026-08-26_haiku_r1_beta6
306•metrofun•15h ago•88 comments

OpenClaw 2.0, Accidentally

https://openclaw.ai/blog/openclaw-2-accidentally
69•doppp•4h ago•69 comments

Show HN: NFC Energy-Harvesting PCB Business Card with an MCU

https://wilsonharper.net/projects/businesscard/
158•WilsonHarper•2d ago•15 comments

How to build a diffusion language model

https://kuleshov-group.github.io/blog/blog/2026/how-to-build-a-diffusion-language-model/
64•volodia•8h ago•5 comments

Cores in space: The core memory module from a 1980 Spacelab computer

https://www.righto.com/2026/08/spacelab-core-memory.html
101•pwg•11h ago•17 comments

Hacking IKEA Furniture

https://greenlightning.eu/diy/hacking-ikea-furniture/
304•greenlightning•20h ago•210 comments

Sort branches by last commit date

https://ryangreenberg.com/til/git-branches-by-commit-date/
112•speckx•5d ago•43 comments

Why open source rocks – a new SM750 (Silicon Motion GPU) HDMI Driver

https://github.com/KodeMunkie/sm750hdmifb
102•SillyUsername•13h ago•36 comments

Continuous Diffusion Language Models (CDLM's)

https://sander.ai/2026/08/24/continuous-dlms.html
90•peter_d_sherman•11h ago•34 comments

What 2000 Buried Underpants Revealed About Where Soil Is Most Alive

https://studyfinds.com/what-2000-buried-underpants-revealed-about-where-soil-is-most-alive/
4•mdp2021•3d ago•1 comments

Relm4 makes developing beautiful cross-platform applications idiomatic

https://relm4.org/
33•Bluestein•4d ago•17 comments

Internet centralization and the original sin of NAT

https://dreamstation.systems/personal/ntppost.html
47•robinpie•5h ago•27 comments

Coordination Headwind: How Organizations Are Like Slime Molds

https://komoroske.com/slime-mold/
152•rzk•15h ago•45 comments

How would you know whether an ancient culture had zero?

https://www.johndcook.com/blog/2026/08/21/ancient-number-system/
52•ibobev•3d ago•25 comments

Show HN: Prove your code produced your claims without making reviewers rerun it

https://github.com/27-GROUP/kveritas-go/
9•Mkld27•5h ago•4 comments

Dad’s Custom Atari Peripherals

https://www.goto10retro.com/p/dads-custom-atari-peripherals
128•rbanffy•3d ago•16 comments

Arbitrary code execution in QubesOS via copy-to-VM error reporting backchannel

https://www.qubes-os.org/news/2026/08/29/qsb-118/
225•vntok•22h ago•90 comments

Racter (1984)

https://www.ubu.com/historical/racter/index.html
23•buescher•2d ago•6 comments

Zig: Pointer Stability for ArrayLists

https://ziglang.org/devlog/2026/#2026-08-27
104•tosh•17h ago•65 comments

Longest Straight Line Paths on Water or Land on the Earth (2018)

https://arxiv.org/abs/1804.07389
203•joebig•23h ago•58 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.