frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Meta enables ADB on deprecated Portal devices [video]

https://fb.watch/HxPu0fSyeH/
121•jenders•3h ago•28 comments

Anthropic's open-source framework for AI-powered vulnerability discovery

https://github.com/anthropics/defending-code-reference-harness
319•binyu•8h ago•102 comments

Do transformers need three projections? Systematic study of QKV variants

https://arxiv.org/abs/2606.04032
125•Anon84•5h ago•20 comments

Azure Linux 4.0 is Microsoft's first general-purpose Linux

https://www.boxofcables.dev/azure-linux-4-0-is-microsofts-first-general-purpose-linux/
13•haydenbarnes•1h ago•7 comments

Open Code Review – An AI-powered code review CLI tool

https://github.com/alibaba/open-code-review
84•geoffbp•4h ago•20 comments

VoidZero Is Joining Cloudflare

https://blog.cloudflare.com/voidzero-joins-cloudflare/
592•coloneltcb•15h ago•263 comments

I'm skeptical about efforts to revolutionize schooling

https://www.scotthyoung.com/blog/2026/05/27/revolutionize-schooling/
95•andrewstuart•2d ago•162 comments

South Korean Forums Will Need to Scan Every Images with AI Censorship Tools

https://discuss.privacyguides.net/t/south-korean-online-communities-will-need-to-scan-every-image...
58•Cider9986•4h ago•24 comments

Branchless Quicksort faster than std:sort and pdqsort with C and C++ API

https://tiki.li/blog/blqsort
116•birdculture•2d ago•18 comments

Reverse-Engineered Userspace Driver for Asus ZenVision Lid OLED on Linux"

https://github.com/tarpediem/zenvision-linux
33•berlianta•2d ago•4 comments

Ian's Secure Shoelace Knot

https://www.fieggen.com/shoelace/secureknot.htm
532•mooreds•16h ago•203 comments

The Causes of Long Covid

https://www.science.org/content/blog-post/causes-long-covid
24•maxall4•1h ago•5 comments

SpaceX, Other Mega IPOs Denied Fast Index Entry by S&P

https://www.bloomberg.com/news/articles/2026-06-04/s-p-dow-jones-keeps-megacap-ipo-rules-as-is-af...
222•tristanj•5h ago•103 comments

Queen bees emerge from special wax chambers

https://cen.acs.org/materials/biobased-materials/queen-bees-special-wax/104/web/2026/06
57•gmays•6h ago•8 comments

When AI Builds Itself: Our progress toward recursive self-improvement

https://www.anthropic.com/institute/recursive-self-improvement
383•meetpateltech•11h ago•506 comments

Samurai City

https://worksinprogress.co/issue/samurai-city/
124•zdw•2d ago•21 comments

KVarN: Native vLLM backend for KV-cache quantization by Huawei

https://github.com/huawei-csl/KVarN
120•theanonymousone•12h ago•12 comments

Retro-Tech Parenting

https://havenweb.org/2026/05/28/retro-tech.html
271•mawise•12h ago•182 comments

I made a kernel 2.2x faster. It made my training loop 3x slower

https://kyrieblunders.bearblog.dev/making-dr-grpo-go-brrr/
15•vishal-padia•2d ago•1 comments

What happens if Japan takes in zero immigrants?

https://www.konichivalue.com/p/what-happens-if-japan-takes-in-zero
12•Konichivalue•2h ago•5 comments

Go Experiments Explained

https://www.alexedwards.net/blog/go-experiments-explained
3•ingve•3d ago•0 comments

JLink JTAG Access on the Pinecil

https://danielmangum.com/posts/jlink-jtag-pinecil/
46•hasheddan•2d ago•8 comments

Castor: CERN Advanced STORage Manager

https://castor.web.cern.ch/content/home.html
46•naves•8h ago•20 comments

Show HN: Uruky (EU-based Kagi alternative) now has Image Search and URL Rewrites

https://uruky.com/?il=en
219•BrunoBernardino•19h ago•198 comments

Making Debian or Fedora persistent live images

https://sigwait.org/~alex/blog/2026/05/28/smdBC8.html
67•henry_flower•3d ago•7 comments

Show HN: Mercek – A Desktop IDE for AWS ECS

https://www.mercek.dev/
35•utibeumanah•7h ago•8 comments

IPv6 zones in URLs are a mistake

https://xeiaso.net/notes/2026/ipv6-zones-go-url/
104•xena•6h ago•79 comments

Zettascale (YC S24) Is Hiring Founding FPGA Engineers

https://www.ycombinator.com/companies/zettascale/jobs/O9S1vqO-founding-engineer-fpga-rtl-asic-arc...
1•el_al•11h ago

Latent Agents: A Post-Training Procedure for Internalized Multi-Agent Debate

https://arxiv.org/abs/2604.24881
19•PaulHoule•5h ago•0 comments

U.S. Army Corps of Engineers Bay Model

https://en.wikipedia.org/wiki/U.S._Army_Corps_of_Engineers_Bay_Model
223•tosh•2d 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.