frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Can you stop beans from making you gassy?

https://www.seriouseats.com/how-to-reduce-bean-gas-tested-11883862
70•jstrieb•2h ago•40 comments

The Free Universal Construction Kit

https://fffff.at/free-universal-construction-kit/
204•robinhouston•3d ago•40 comments

1-Bit Hokusai's "The Great Wave" (2023)

https://www.hypertalking.com/2023/05/08/1-bit-pixel-art-of-hokusais-the-great-wave-off-kanagawa/
488•stephen-hill•3d ago•83 comments

Using coding assistance tools to revive projects you never were going to finish

https://blog.matthewbrunelle.com/its-ok-to-use-coding-assistance-tools-to-revive-the-projects-you...
105•speckx•6h ago•73 comments

New 10 GbE USB adapters are cooler, smaller, cheaper

https://www.jeffgeerling.com/blog/2026/new-10-gbe-usb-adapters-cooler-smaller-cheaper/
513•calcifer•16h ago•303 comments

The Joy of Folding Bikes

https://blog.korny.info/2026/04/19/the-joy-of-folding-bikes
17•pavel_lishin•3d ago•1 comments

Mine, an IDE for Coalton and Common Lisp

https://coalton-lang.github.io/mine/
42•varjag•4h ago•4 comments

Simulacrum of Knowledge Work

https://blog.happyfellow.dev/simulacrum-of-knowledge-work/
56•thehappyfellow•5h ago•21 comments

Desmond Morris has died

https://www.bbc.com/news/articles/c51y797v200o
79•martey•5d ago•13 comments

Martin Galway's music source files from 1980's Commodore 64 games

https://github.com/MartinGalway/C64_music
149•ingve•11h ago•19 comments

How Hard Is It to Open a File?

https://blog.sebastianwick.net/posts/how-hard-is-it-to-open-a-file/
26•ffin•1d ago•2 comments

GPT‑5.5 Bio Bug Bounty

https://openai.com/index/gpt-5-5-bio-bug-bounty/
116•Murfalo•8h ago•90 comments

Discret 11, the French TV encryption of the 80s

https://fabiensanglard.net/discret11/
134•adunk•11h ago•21 comments

Show HN: Kloak, A secret manager that keeps K8s workload away from secrets

https://getkloak.io/
27•neo2006•3h ago•22 comments

What async promised and what it delivered

https://causality.blog/essays/what-async-promised/
115•zdw•3d ago•110 comments

Lute: A Standalone Runtime for Luau

https://lute.luau.org/
38•vrn-sn•2d ago•7 comments

Which one is more important: more parameters or more computation? (2021)

https://parl.ai/projects/params_vs_compute/
39•jxmorris12•1d ago•6 comments

Hokusai and Tesselations

https://dl.ndl.go.jp/pid/1899550/1/11/
83•srean•5h ago•13 comments

America's Geothermal Breakthrough Could Unlock a 150-Gigawatt Energy Revolution

https://oilprice.com/Alternative-Energy/Geothermal-Energy/Americas-Geothermal-Breakthrough-Could-...
35•sleepyguy•2h ago•20 comments

Insights into firewood use by early Middle Pleistocene hominins

https://www.sciencedirect.com/science/article/pii/S0277379126001824
44•wslh•3d ago•18 comments

A web-based RDP client built with Go WebAssembly and grdp

https://github.com/nakagami/grdpwasm
97•mariuz•11h ago•40 comments

Only one side will be the true successor to MS-DOS – Windows 2.x

https://blisscast.wordpress.com/2026/04/21/windows-2-gui-wonderland-12a/
66•keepamovin•11h ago•47 comments

Plain text has been around for decades and it’s here to stay

https://unsung.aresluna.org/plain-text-has-been-around-for-decades-and-its-here-to-stay/
256•rbanffy•21h ago•127 comments

The AI Industry Is Discovering That the Public Hates It

https://newrepublic.com/article/209163/ai-industry-discovering-public-backlash
141•chirau•1h ago•163 comments

North American Millets Alliance(2023)

https://milletsalliance.org/
8•num42•4h ago•2 comments

Replace IBM Quantum back end with /dev/urandom

https://github.com/yuvadm/quantumslop/blob/25ad2e76ae58baa96f6219742459407db9dd17f5/URANDOM_DEMO.md
323•pigeons•21h ago•44 comments

Lambda Calculus Benchmark for AI

https://victortaelin.github.io/lambench/
122•marvinborner•11h ago•37 comments

HEALPix

https://en.wikipedia.org/wiki/HEALPix
47•hyperific•9h ago•6 comments

Commenting and approving pull requests

https://www.jakeworth.com/posts/on-commenting-and-approving-pull-requests/
74•jwworth•2d ago•61 comments

Sabotaging projects by overthinking, scope creep, and structural diffing

https://kevinlynagh.com/newsletter/2026_04_overthinking/
508•alcazar•1d ago•129 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•11mo ago

Comments

tonyarkles•11mo 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•11mo ago
You can convert edge coloring problems into vertex coloring problems and vice versa through a simple O(n) procedure.
meindnoch•11mo 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•11mo ago
Indeed. Thanks, I stand corrected.
tonyarkles•11mo 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•11mo 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•11mo 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•11mo ago
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•11mo 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•11mo 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•11mo 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.
phkahler•11mo ago
Is this going to lead to faster compile times? Faster register allocation...
john-h-k•11mo ago
Very few compilers actually use vertex coloring for register allocation
isaacimagine•11mo 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•11mo ago
and this post isn't even about vertex coloring
DannyBee•11mo 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.