frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Claude Opus 4.8

https://www.anthropic.com/news/claude-opus-4-8
958•craigmart•4h ago•766 comments

Bricks and Minifigs Stole a Man's $200k Lego Collection

https://mybricklog.com/blog/bricks-minifigs-corporate-stole-old-mans-200000-lego-collection
234•philips•1h ago•81 comments

Just Use Postgres for Durable Workflows

https://www.dbos.dev/blog/postgres-is-all-you-need-for-durable-execution
169•KraftyOne•2h ago•56 comments

Social Animus

https://justine.lol/animus/
32•jart•50m ago•0 comments

Nitpicking the shell history scene in 'Tron: Legacy'

https://www.chiark.greenend.org.uk/~sgtatham/quasiblog/tron-legacy/
60•speckx•1h ago•10 comments

Various LLM Smells

https://shvbsle.in/various-llm-smells/
35•speckx•2h ago•15 comments

Bitburner, programming-based incremental game

https://bitburner-official.github.io/
48•agmater•3h ago•6 comments

I hated writing–until I learned there's a science to it(2024)

https://www.science.org/content/article/i-hated-writing-until-i-learned-there-s-science-it
69•o4c•3h ago•21 comments

News about Raspberry Pi 6 and Microcontroller Development

https://www.jeffgeerling.com/blog/2026/news-about-raspberry-pi-6-and-microcontroller-development/
96•rbanffy•2d ago•66 comments

Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue

https://llmgame.scalex.dev
183•Wirbelwind•8h ago•90 comments

The Permanent Upper Crow

https://permanent-upper-crow.jasonwu.ink/
117•whiteblossom•5h ago•40 comments

Caio, a cleaner search engine for 500k+ tech jobs

https://caio-jobs.com/
18•danicuki•1h ago•4 comments

Separate the Cord from the Device

https://bookofjoe2.blogspot.com/2026/05/blog-post_27.html
13•bookofjoe•1h ago•12 comments

Indoor Wi-Fi Roaming with OpenWRT

https://taoofmac.com/space/blog/2026/05/26/1730
180•zdw•2d ago•88 comments

Sam Altman and Dario Amodei are both walking back AI jobs apocalypse predictions

https://fortune.com/2026/05/26/sam-altman-dario-amodei-walking-back-ai-jobs-apocalypse-prophecies...
71•ianrahman•1h ago•56 comments

Show HN: Ktx – Open-source executable context layer for data agents

https://github.com/Kaelio/ktx
35•lucamrtl•6h ago•5 comments

The Most Unlikely School Bag

https://www.carryology.com/insights/carry-culture/the-tale-of-the-worlds-most-unlikely-school-bag/
35•surprisetalk•3d ago•15 comments

Endive: A JVM native WebAssembly runtime

https://github.com/bytecodealliance/endive
34•theanonymousone•4h ago•10 comments

Ask HN: Entrepreneurs, how long did it take you to succeed?

17•asdev•25m ago•5 comments

The Lone Lisp Heap

https://www.matheusmoreira.com/articles/lone-lisp-heap
18•stevekemp•2h ago•6 comments

Confidence Scores for Exam Questions

https://nomagicpill.substack.com/p/confidence-scores-for-exam-questions
4•surprisetalk•3d ago•2 comments

EU fines Temu €200M for allowing sale of illegal products

https://www.bbc.co.uk/news/articles/c1k2ydn1rz8o
265•jjp•6h ago•190 comments

Show HN: Hallucinate – Massively Multiplayer Online Rave

https://hallucinate.site
390•stagas•17h ago•174 comments

Using Tailscale with an OrbStack VM on macOS

https://github.com/highpost/tailscale-macos-vm
39•highpost•2d ago•8 comments

Dynamic Workflows in Claude Code

https://claude.com/blog/introducing-dynamic-workflows-in-claude-code
120•mil22•4h ago•92 comments

Trivial Pursuits

https://www.lrb.co.uk/the-paper/v48/n10/david-runciman/trivial-pursuits
20•diodorus•4h ago•6 comments

Legislation Killed Would Have Effectively Blocked Police LPR, Including Flock

https://ipvm.com/reports/bipartisan-alpr-amendment-killed
64•jhonovich•4h ago•41 comments

Anthropic raises $65B in Series H funding at $965B post-money valuation

https://www.anthropic.com/news/series-h
170•meetpateltech•3h ago•146 comments

YouTube to automatically label AI-generated videos

https://blog.youtube/news-and-events/improving-ai-labels-viewers-creators/
1250•nopg•1d ago•745 comments

Show HN: Open-Source AI Racing Harness

https://www.elodin.systems/post/elodin-ai-grand-prix-race-sim-harness
61•danAtElodin•1d ago•7 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.