frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

My server is a phone now

https://seg6.space/posts/phone-server/
138•seg6•4h ago•58 comments

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

https://os8088.com/
71•jggonz•3h ago•26 comments

Improving Heuristics for A* Pathfinding

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

The phone book that led us to Assad's spy chief in hiding

https://www.bbc.com/news/articles/c4gyrzn8p94o
18•cwwc•1h ago•4 comments

Fastmail offers EU data region

https://www.fastmail.com/blog/fastmail-offers-eu-data-region/
333•groomlake•11h ago•159 comments

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

https://shopify.engineering/scaling-inventory-reservations
69•adletbalzhanov•4h ago•29 comments

Dithered QR Codes

https://www.andrewt.net/dithered-qr-codes/wtf/
51•jmusall•4h ago•9 comments

_for-sale DNS records

https://specification.website/spec/foundations/for-sale-dns/
360•shaunpud•13h ago•134 comments

The Sound and Music of 'Hyper Light Drifter' [video]

https://gdcvault.com/play/1024135/The-Sound-and-Music-of
27•hyperific•3d ago•4 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...
97•MarcoDewey•7h ago•20 comments

Making difficulty curves in games

http://www.davetech.co.uk/difficultycurves
71•hakkikonu•3d ago•24 comments

Timeline of the OpenAI accidental attack against Hugging Face

https://simonwillison.net/2026/Aug/7/openai-timeline/
356•882542F3884314B•16h ago•358 comments

Unexpected events and prosocial behavior: the Batman effect

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

Can Intel finally beat ARM on performance per Watt?

https://hackaday.com/2026/08/08/want-energy-efficiency-dude-youre-getting-a-dell/
174•gumby•11h ago•121 comments

Should you stop cracking your knuckles?

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

US Military's cyber command unit grapples with cluster of deaths by suicide

https://www.bloomberg.com/news/articles/2026-08-06/us-military-s-cyber-command-unit-grapples-with...
257•rbanffy•17h ago•406 comments

Triton: DirectX 11 Driver for QEMU

https://blog.getutm.app/2026/introducing-triton-directx-11-driver-for-qemu/
144•electricant•13h ago•27 comments

Building a local positioning system to track runners using Ultra-Wideband

https://zeus.ugent.be/blog/25-26/12urenloop-uwb/
48•robinpdev•1w ago•3 comments

Preventing Misfolding by Preventing Folding

https://www.science.org/content/blog-post/preventing-misfolding-preventing-folding
49•surprisetalk•4d ago•2 comments

TheoremDB · A public workspace for machine mathematics

https://theoremdb.org/
6•frozenseven•1h ago•0 comments

DDisasm: Reversible (bi-directional) Disassembler

https://github.com/GrammaTech/ddisasm
23•aboardRat4•5d ago•4 comments

Maryland Closes More of Cunningham Falls State Park After Second Beaver Attack

https://news.maryland.gov/dnr/2026/08/05/dnr-closes-additional-areas-of-cunningham-falls-state-pa...
99•bookofjoe•6h ago•60 comments

Gateway 2000's hilariously bad ads in the 90s (Part II)

https://buttondown.com/suchbadtechads/archive/gateway-2000-part-2/
106•rfarley04•14h ago•84 comments

TinySol, a tiny solitaire game for DOS

https://classicbits.net/coding-and-software/my-software/monosol/
50•skibz•9h ago•13 comments

Danish high schoolers will have to verbally defend written assignments

https://mezha.net/eng/bukvy/ca117584_denmark_requires_oral/
526•theanonymousone•9h ago•248 comments

“Code was never the hard part” is an insult to all programmers

https://blog.senko.net/code-was-never-the-hard-part-is-an-insult-to-all-programmers
603•senko•12h ago•374 comments

Lost my phone at the office. Claude suggested tracking Bluetooth signal strength

https://twitter.com/un1c0rnioz/status/2084686552299634805
231•ilamont•1d ago•164 comments

Title 7 Disparate Impact Liability Makes Almost Everything Presumptively Illegal

https://www.nyujll.com/volume-14/title-vii-disparate-impact-liability-makes-almost-everything-pre...
25•like_any_other•3h ago•21 comments

Message your other Claude Code sessions

https://code.claude.com/docs/en/cross-session-messaging
71•mfiguiere•11h ago•33 comments

When Feature Flags Do and Don't Make Sense

https://software.rajivprab.com/2019/12/19/when-feature-flags-do-and-dont-make-sense/
10•whack•5d ago•5 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.