frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Mea Culpa – Dark Hours

https://blog.terrygodier.com/2026/08/09/mea-culpa-dark-hours.html
215•satvikpendem•2h ago•99 comments

Show HN: A Project Oberon System version running on RISC-V instead of RISC-5

https://github.com/rochus-keller/OberonSystem/tree/op2-rv32
48•Rochus•3h ago•13 comments

John C. Lilly on solid state intelligence and the elimination of man (1978)

https://kibotronics.net/unlisted/lilly-machines/
23•Kiboneu•2h ago•7 comments

There Are Magic Hexagons of Every Order

https://gukov.dev/math/2026/08/02/new-magic-hexagons.html
132•gukoff•8h ago•20 comments

Honey, I shrunk the embeddings: Matryoshka vs. PCA

https://dylancastillo.co/posts/matryoshka-vs-pca
31•dcastm•6d ago•3 comments

Silicon Valley misreads science fiction and undermines democracy

https://techcrunch.com/2026/08/09/historian-jill-lepore-says-the-tech-industry-is-led-by-bad-read...
28•evo_9•41m ago•4 comments

My server is a phone now

https://seg6.space/posts/phone-server/
432•seg6•17h ago•198 comments

The Alpha 21264 CPU: NT's Greatest RISC (1998)

https://halfhill.com/byte/1998-12_alpha.html
50•Lammy•5h ago•26 comments

Microsoft Word for Windows 1.1a, Native X64 Port

https://github.com/jmarshall23/msword
122•BruceEel•10h ago•53 comments

Os8088: A powerful Mac-like OS for the IBM XT, 286, 386

https://os8088.com/
220•jggonz•16h ago•144 comments

Uber SubmitQueue: a high-performance speculative merge queue

https://github.com/uber/submitqueue/
56•handfuloflight•1w ago•40 comments

The Grid That Doubles the Strength of the Ground

https://practical.engineering/blog/2026/8/4/the-grid-that-doubles-the-strength-of-the-ground
94•michaefe•4d ago•20 comments

Fastmail offers EU data region

https://www.fastmail.com/blog/fastmail-offers-eu-data-region/
475•groomlake•23h ago•274 comments

Dithered QR Codes

https://www.andrewt.net/dithered-qr-codes/wtf/
318•jmusall•16h ago•33 comments

Improving Heuristics for A* Pathfinding

https://www.redblobgames.com/pathfinding/heuristics/differential.html
318•bobbiechen•1w ago•35 comments

Reviving a four year old reMarkable 2

https://oskrim.github.io/hardware/2026/08/09/remarkable-over-ssh.html
78•tremguy•4h ago•59 comments

Shopify replaced Redis with MySQL for inventory reservations–and it scaled

https://shopify.engineering/scaling-inventory-reservations
293•adletbalzhanov•17h ago•192 comments

Tom Stanton's supersonic trebuchet breaks sound barrier with gravity alone

https://www.techeblog.com/tom-stanton-supersonic-trebuchet/
13•Thorondor•50m ago•2 comments

TheoremDB – A public workspace for machine mathematics

https://theoremdb.org/
74•frozenseven•14h ago•9 comments

The original URL for this prediction will no longer be available in 11 years (2011)

http://longbets.org/601/
184•doubletwoyou•11h ago•87 comments

Stylized GGX Shading

https://alexandrelamure.github.io/graphics-posts/stylized-ggx-shading.html
50•ibobev•5d ago•0 comments

Making difficulty curves in games

http://www.davetech.co.uk/difficultycurves
148•hakkikonu•4d ago•68 comments

Unexpected events and prosocial behavior: the Batman effect (2025)

https://www.nature.com/articles/s44184-025-00171-5
77•davidbarker•6d ago•25 comments

Should you stop cracking your knuckles?

https://www.bbc.com/future/article/20260807-should-i-stop-cracking-my-knuckles
94•tchalla•17h ago•99 comments

Open-source interactive map for the Aug 12 total solar eclipse

https://eclipsefan.org/?v=2&t=max&layers=eclipse%2Cbesselian%2Cumbra-live%2Cshadow-3d%2Ccloud-pro...
180•MarcoDewey•20h ago•59 comments

CSS: The bomb inside your inbox

https://portswigger.net/research/css-the-bomb-inside-your-inbox
73•ashurandi•5h ago•22 comments

Show HN: Airy – Free, fast, and simple voice content creation

https://airy.so
17•login588•6h ago•11 comments

Protopia

https://kevinkelly.substack.com/p/protopia
46•surprisetalk•5d ago•40 comments

Taxi drivers rarely die of Alzheimer's

https://theconversation.com/taxi-drivers-rarely-die-of-alzheimers-how-complex-mental-maps-and-spa...
5•jader201•37m ago•0 comments

Triton: DirectX 11 Driver for QEMU

https://blog.getutm.app/2026/introducing-triton-directx-11-driver-for-qemu/
199•electricant•1d ago•44 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.