frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Tiny Emulators

https://floooh.github.io/tiny8bit-preview/index.html
29•naves•33m ago•0 comments

Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k

https://systima.ai/blog/claude-code-vs-opencode-token-overhead
257•systima•2h ago•137 comments

I love LLMs, I hate hype

https://geohot.github.io//blog/jekyll/update/2026/07/12/i-love-llms.html
180•therepanic•2h ago•91 comments

Old and new apps, via modern coding agents

https://terrytao.wordpress.com/2026/07/11/old-and-new-apps-via-modern-coding-agents/
372•subset•9h ago•104 comments

The One-Step Trap (In AI Research)

http://incompleteideas.net/IncIdeas/OneStepTrap.html
22•jxmorris12•2h ago•3 comments

I Learned to Read Again

https://substack.magazinenongrata.com/p/how-i-learned-to-read-again
35•georgex7•2h ago•5 comments

Against Usefulness

https://www.motivenotes.ai/p/against-usefulness
53•supo•3h ago•12 comments

LARP – Revenue infrastructure for serious founders

https://www.larp.website/
78•BerislavLopac•3h ago•14 comments

Automation Without Understanding

https://arxiv.org/abs/2607.06377
65•root-parent•4h ago•33 comments

Why write code in 2026

https://softwaredoug.com/blog/2026/07/09/write-code
51•softwaredoug•2d ago•99 comments

Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper

https://ploy.ai/blog/migrating-a-production-ai-agent-to-gpt-5-6
38•brryant•3h ago•7 comments

Don't you mean extinct?

https://fabiensanglard.net/extinct/index.html
151•zdw•5h ago•80 comments

Defining new Jax types with hijax

https://docs.jax.dev/en/latest/hijax_types.html
6•fhchl•1h ago•0 comments

Show HN: Nectar, a Rust-like React that compiles to WebAssembly

https://buildnectar.com
20•blakeburnette•6d ago•8 comments

Irish datacenters now guzzle 23% of the country's electricity

https://www.theregister.com/on-prem/2026/07/11/irish-datacenters-now-guzzle-23-of-the-countrys-el...
27•Bender•40m ago•17 comments

Neocities: Create your own free website

https://neocities.org/
42•Tomte•1h ago•6 comments

The shingles vaccine may reduce the risk of dementia

https://www.economist.com/leaders/2026/07/09/a-no-brainer-for-protecting-your-brain
167•saikatsg•5h ago•123 comments

How to read more books

https://scotto.me/blog/2026-07-12-how-to-read-more-books/
203•silcoon•5h ago•117 comments

Why study Diophantine equations?

https://hidden-phenomena.com/articles/modular
52•mb1699•5h ago•17 comments

Deir El-Medina Strikes

https://en.wikipedia.org/wiki/Deir_el-Medina_strikes
30•mooreds•5d ago•4 comments

Theo de Raadt: "You've been smoking something mind altering" (2007)

https://marc.info/?l=openbsd-misc&m=119318909016582
65•turrini•4h ago•58 comments

The power of collaboration: How we can reduce traffic congestion

https://research.google/blog/the-power-of-collaboration-how-we-can-reduce-traffic-congestion/
41•raahelb•5h ago•31 comments

Understanding the Odin programming language

https://odinbook.com/
132•AlexeyBrin•8h ago•71 comments

The Seed Beneath the Snow

https://eli.li/the-seed-beneath-the-snow
4•surprisetalk•3d ago•0 comments

Ghostel.el: Terminal emulator powered by libghostty

https://dakra.github.io/ghostel/
245•signa11•12h ago•42 comments

Show HN: Shirei, cross-platform GUI framework in native Go

https://github.com/hasenj/go-shirei/
66•hsn915•4h ago•36 comments

Vint Cerf, “father of the Internet”, is retiring

https://techcrunch.com/2026/06/30/the-father-of-the-internet-is-finally-retiring/
262•compiler-guy•2d ago•151 comments

Can We Understand How Large Language Models Reason?

https://cacm.acm.org/news/can-we-understand-how-large-language-models-reason/
47•adunk•2h ago•46 comments

What xAI's Grok build CLI sends to xAI: A wire-level analysis

https://gist.github.com/cereblab/dc9a40bc26120f4540e4e09b75ffb547
374•jhoho•19h ago•149 comments

Croc: Securely transfer files and folders between two computers

https://github.com/schollz/croc/
25•gregsadetsky•5h ago•12 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.