frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

HackerTube: YouTube built from videos recommended by HN

https://karpathy.bearblog.dev/hacker-tube/
1249•karpathy•13h ago•360 comments

An Italian farmer found some unknown seeds in his attic and planted them

https://www.smithsonianmag.com/science-nature/italian-farmer-found-unknown-seeds-attic-with-nothi...
403•ecares•10h ago•115 comments

The AI cost of JavaScript frameworks

https://nolanlawson.com/2026/10/28/the-ai-cost-of-javascript-frameworks/
45•luu•3h ago•24 comments

Running a bootstrapped SaaS for 20 years with my brother

https://blog.zamzar.com/2026/10/30/20-years-766-million-files-two-chameleons/
72•whyleyc•1d ago•20 comments

Brazilian Court Sanctions Lawyers for Prompt Injection in Court Filing

https://jetstream.security/insights/brazilian-court-sanctions-prompt-injection-filing/
109•doodlesdev•6h ago•43 comments

TCP Use-After-Free: CVE-2026-98432 / CVSS 9.8

https://atlasum.net/blog/cve-2026-98432-linux-ipv4-tcp-uaf
496•oger•14h ago•227 comments

Memdoor: A team of 5 Qwen3.8-27B models beats Fable 5 on LiveCodeBench Hard

https://github.com/guregodevo/memdoor/tree/main/examples/workflows/team-solve
216•guregodevo•10h ago•107 comments

Leaking Secrets from Air-Gap Computers by Spelling Radio Signals from RAM (2024)

https://arxiv.org/abs/2409.02292
78•hapax_legomena•7h ago•36 comments

Pac-Man's Siren Call

https://unsung.aresluna.org/pac-mans-siren-call/
13•tobr•2h ago•3 comments

Zinc creep in cable spelter sockets brought down the Arecibo telescope in 2020

https://maketecheasier.com/arecibo-zinc-creep-collapse/
104•ohjeez•1d ago•26 comments

Altoids Project

https://uvdn7.github.io/altoids-project/
108•uvdn7•10h ago•4 comments

ChatGPT and Codex usage limits merging

https://help.openai.com/en/articles/20001625-understanding-chatgpt-and-codex-usage-limits
111•Zariel•11h ago•52 comments

It's the memory latency, stupid

https://pivotlake.io/blog/its-the-memory-latency-stupid/
189•ntur1337•14h ago•56 comments

A 1580 Map Shows Why Data Visualization Is Never Neutral

https://thereader.mitpress.mit.edu/a-1580-map-shows-why-data-visualization-is-never-neutral/
37•the-mitr•1d ago•2 comments

Pilot-wave hydrodynamics (Quantum phenomena in macroscopic hydrodynamic systems)

http://thales.mit.edu/bush/index.php/4801-2/
32•peter_d_sherman•1d ago•3 comments

A brief history of just-in-time: forty years of JIT work, from 1960–2000

https://dl.acm.org/doi/10.1145/857076.857077
24•gjvc•2d ago•0 comments

Jepsen: ParticleDB 1.1.4

https://jepsen.io/analyses/particledb-1.1.4
260•aphyr•19h ago•149 comments

Electrification Could Cut Global Energy Use in Half

https://fullycharged.show/podcasts/podcast-361-why-electrification-could-cut-global-energy-use-in...
98•toomuchtodo•14h ago•43 comments

Surviving "The Graduate"

https://www.newyorker.com/culture/the-weekend-essay/dustin-hoffman-on-surviving-the-graduate
114•samizdis•13h ago•35 comments

Understanding Email Encryption

https://www.fastmail.com/blog/email-encryption/
8•nmjenkins•1d ago•1 comments

OTape

https://www.otape.org/
26•dotmanish•6h ago•14 comments

Edgar Allan Poe, Quintessential American Writer

https://slate.com/culture/2026/10/edgar-allan-poe-poems-stories-most-influential-american-writer-...
31•samclemens•3d ago•1 comments

Do the math: How we took over ChatGPT accounts

https://www.parameter.ai/labs/we-found-a-gap-at-openai
327•armcat•22h ago•163 comments

Simple circuits can create complex behaviors

https://aatishb.com/myriad/lets-build-a-brain/
246•aatish•4d ago•77 comments

The Duty of a Scholar

https://www.daemonology.net/blog/2026-10-31-The-Duty-of-a-Scholar.html
117•gslin•14h ago•32 comments

Show HN: NES Contra (1987) port (ASM –> C and then C –> WebAssembly)

https://epoyraz.github.io/nes-contra-us/
83•tevlon•13h ago•57 comments

Show HN: BBRouter – Ben Eater's 8-bit computer, simulated on 3D breadboards

https://bbrouter.com/bbrouter/ben-eater-sap-1
29•creack•9h ago•8 comments

Anthropic blocks users for anything touching training larger models

https://twitter.com/jiahaoshao1/status/2116475922190922088
338•pretext•13h ago•191 comments

Reading and writing are less symmetric than you (probably) think

https://fgiesen.wordpress.com/2015/10/25/reading-and-writing-are-less-symmetric-than-you-probably...
111•luu•3d ago•26 comments

Decode kernel panic from QR Code photo

https://gist.github.com/skorotkiewicz/c59e591c26661cb52b06afc42d8ac546
29•modinfo•1d ago•10 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.