frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Whatever became of holography? (2011)

https://www.americanscientist.org/article/whatever-became-of-holography
64•cainxinth•2h ago•22 comments

Total Annihilation, rebuilt for modern computers

https://nanolathe.gg
368•jttnr•7h ago•155 comments

Cartographers of North Korea (2019)

https://cartographers-nk.wonyoung.so/
188•edent•6h ago•32 comments

Fingerprints are the new cookies

https://royfish.dev/fingerprints-are-the-new-cookies
86•royfish•3h ago•35 comments

Recursive self-improvement through collective intelligence

https://pub.sakana.ai/mass/
62•hardmaru•3h ago•27 comments

HashiCorp archives the Boundary open source repo

https://github.com/hashicorp/boundary
29•vmatsiiako•1h ago•1 comments

The gap in shared understanding of LLM capability is widening

https://twitter.com/karpathy/status/2109361546505966046
255•albertzeyer•5h ago•408 comments

Illustration Beyond Proof

https://terrytao.wordpress.com/2026/10/11/illustration-beyond-proof/
25•smilelamp•2h ago•0 comments

Local Indexing to reduce tool calling and token usage

https://tedhaley.ca/pensieve/
20•TedHaley•1h ago•3 comments

Terence Tao: Math 2.0 [pdf]

https://teorth.github.io/tao-web/slides/math-2-0-caltech-2026.pdf
322•Anon84•12h ago•372 comments

Passkeys are a trap

https://nonfunctional.substack.com/p/passkeys-are-a-trap-do-not-use-them
276•laurex•4h ago•153 comments

So, You’d Like To Sell Your Print Issues Of The Onion?

https://theonion.com/archivehunt/
252•mooreds•6h ago•36 comments

Google is illegaly cutting forest to build data centers

https://www.theguardian.com/technology/2026/oct/06/google-datacentres-finland-temporary-halt-envi...
138•heyimada•3h ago•18 comments

Chapter 1 of "Ways of Seeing" by John Berger (1972)

https://www.ways-of-seeing.com/ch1
76•rafael859•7h ago•12 comments

Programmable pigments: Photochromic nanoparticle inks for rewritable tattoos

https://www.cell.com/matter-light/fulltext/S3117-5848(26)00119-5
14•Bluestein•16h ago•1 comments

NYC's "Click to Cancel" rule is now in effect

https://www.nyc.gov/main/click-to-cancel
354•gregsadetsky•7h ago•172 comments

Qt An E2EE post-quantum messenger core in Rust (10k connections on 124MB RAM

https://github.com/moral666/QT
8•moral666•2h ago•1 comments

Governments are mishandling the affordability crisis

https://www.economist.com/finance-and-economics/2026/10/08/governments-are-mishandling-the-afford...
57•andsoitis•2h ago•55 comments

I guess I'm using WebP now?

https://anderegg.ca/2026/10/08/i-guess-im-using-webp-now
78•Brajeshwar•2d ago•80 comments

Vectorized CLZ and CTZ

https://purplesyringa.moe/blog/vectorized-clz-and-ctz/
3•zX41ZdbW•22h ago•0 comments

500B tokens later: Letting AI agents decompile a first-person shooter

https://momo5502.com/posts/2026-10-09-game-decompilation/
165•davikr•23h ago•113 comments

Safe SIMD in Rust, even on the inside

https://shnatsel.github.io/safe-simd-in-rust-even-on-the-inside/
37•ravenical•1d ago•2 comments

The tilde in your PATH may not be your HOME

https://disconnect3d.pl//2026/10/02/dont-put-tilde-in-your-path/
214•arusekk•13h ago•142 comments

A Remote Employee Refused 160 Webcam Photos a Day. Her Employer Fired Her

https://www.inc.com/chloe-rosenberg/a-remote-employee-refused-160-webcam-photos-a-day-her-employe...
155•bhrlady•4h ago•113 comments

apsw: Another Python SQLite Wrapper

https://github.com/rogerbinns/apsw
68•tosh•9h ago•15 comments

Show HN: Plimsoll, a self-hosted sandbox for code your AI agent writes

https://github.com/plimsollmark/plimsoll
11•cagster•2h ago•2 comments

Show HN: BetterWispr – Free, open-source dictation for Mac

https://betterwispr.com/
157•kartik017•13h ago•93 comments

FlowCE: Calculus on your TI-84 Plus CE

https://tommyb3ll.github.io/FlowCE/
27•jgx0•1d ago•11 comments

How I reverse engineered a commercial spatial audio effect

http://epestr.com/blog/reverse-engineering-a-commercial-spatial-audio-effect/
99•epestr•10h ago•34 comments

Show HN: BraiNOTES, handwritten notes on your lecture PDFs in a browser tab

https://github.com/swimmingbrain/brainotes
10•swimmingbrain•2h ago•0 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.