frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Reparaible and open source paper printer

https://www.opentools.studio/
90•bouh•1h ago•26 comments

Organic Maps

https://organicmaps.app/
700•tosh•7h ago•200 comments

New AI tutor achieves 0.71-1.30 SD effect size in Dartmouth course [pdf]

https://intextbooks.science.uu.nl/workshop2026/files/itb26_s1s2.pdf
95•jonahbard•3h ago•58 comments

Completing a Computer Science Degree on Coursera

https://notesbylex.com/completing-a-computer-science-degree-on-coursera
24•lexandstuff•48m ago•4 comments

Show HN: Homegames. An open-source game platform I've been making for 8 years

https://homegames.io
17•homegamesjoseph•36m ago•2 comments

The future of Flipper Zero development

https://blog.flipper.net/future-of-flipper-zero-development/
154•croes•3h ago•33 comments

Pint in England

https://dispatch-media.com/the-best-pint-in-england/
14•gripfx•1h ago•1 comments

Mr. Baby Paint and accidentally discovering a new cellular automata

https://tekstien-marginaalien-keskus.aalto.fi/residenssi/heikki/blog/004-december-2/
62•jfil•2d ago•12 comments

Starring the Computer

https://www.starringthecomputer.com/computers.html
135•gitowiec•4h ago•32 comments

Dungeon Proof Crawler: learn how to write proofs with RPG

https://dhilst.github.io/algae/game/index.html
12•SchwKatze•1h ago•5 comments

CoCom regulations and GPS receivers for balloons and cubesats

https://space.stackexchange.com/questions/14687/current-situation-with-cocom-regulations-and-gps-...
6•vinnyglennon•30m ago•0 comments

It's not about physical vs. digital games, it's about ownership

https://popcar.bearblog.dev/its-about-ownership/
223•popcar2•7h ago•167 comments

Show HN: Osint tool that finds exposed files on domains

https://search.cerast-intelligence.com/
14•PatchRequest•1h ago•0 comments

Dependencies should be fetched directly from VCS

https://www.arp242.net/deps-vcs.html
11•mrngm•1h ago•4 comments

DNSGlobe – Rust TUI to watch DNS propagate around the world

https://github.com/514-labs/dnsglobe
3•Callicles•13m ago•0 comments

Cursed circuits #5: capacitance multiplier

https://lcamtuf.substack.com/p/cursed-circuits-capacitance-multiplier
17•surprisetalk•2h ago•0 comments

Introduction to Compilers and Language Design (2021)

https://dthain.github.io/books/compiler/
248•AlexeyBrin•10h ago•42 comments

Papa Johns Can Predict When Your Fridge Is Empty

https://www.adexchanger.com/tv/papa-johns-can-predict-when-your-fridge-is-empty/
28•WaitWaitWha•3d ago•23 comments

You need a webring

https://shub.club/writings/2026/july/you-need-a-webring/
33•forthwall•3h ago•26 comments

Run Windows 2000 on a DEC Alpha with a new es40 fork

https://raymii.org/s/blog/Run_Windows_2000_for_Dec_Alpha_on_a_new_es40_fork.html
87•jandeboevrie•8h ago•46 comments

Installing A/UX 1.1 like it's the 90s

https://thomasw.dev/post/aux11/
41•zdw•6h ago•14 comments

Zero-copy in Go: sendfile, splice, and the cost of io.Copy

https://segflow.github.io/post/zero-copy-sendfile-splice/
11•mrngm•1h ago•0 comments

The great blogging collapse: What happened to 100 successful blogs?

https://danielstanica.com/posts/Great-Blogging-Collapse
132•thm•3d ago•102 comments

We Always Leave Things Unfinished

https://bigreaderbadgrades.substack.com/p/we-always-leave-things-unfinished
18•bryanrasmussen•3d ago•1 comments

How the first solo-founder unicorn gets built

https://www.thisandthat.chat/blog/how-the-first-solo-founder-unicorn-gets-built/
6•jreynar•3d ago•2 comments

Airplane Boneyards List and Map

https://airplaneboneyards.com/airplane-boneyards-list-and-map.htm
72•hyperific•1d ago•12 comments

Jim Keller's startup is building a factory to mass-produce small chip fabs

https://www.tomshardware.com/tech-industry/atomic-semi-rebrands-as-fab2-and-shifts-operations-to-...
72•logickkk1•3h ago•13 comments

Why DMARC's new "NP" tag can fail with DNSSEC

https://dmarcwise.io/blog/dmarc-np-incompatibility-with-dnssec
40•matteocontrini•7h ago•16 comments

Speech and Noise Corpora for Pitch Estimation of Human Speech

https://zenodo.org/records/3920591
6•q7m•2h ago•0 comments

Optimizing an algorithm that's quadratic by design

https://whatchord.earthmanmuons.com/articles/chord-ranking-performance.html
20•elasticdog•3d 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.