frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Codex on AWS bedrock bug causing 10x charges

https://github.com/openai/codex/issues/37674
90•TheP1000•3h ago•27 comments

The August 17 outage

https://github.blog/news-insights/company-news/the-august-17-outage-and-the-work-ahead/
444•0xedb•11h ago•510 comments

I like 'em thick: an apology to my English teachers

https://www.experimental-history.com/p/i-like-em-thick
667•Ariarule•2d ago•277 comments

The Religious Experience of Philip K. Dick by R. Crumb (1986)

https://philipdick.com/resources/miscellaneous/the-religious-experience-of-philip-k-dick-by-r-cru...
10•wise_blood•55m ago•1 comments

HTML Can Do That

https://chrisburnell.com/html-can-do-that/
695•encyclopedism•1d ago•176 comments

Malicious Rust crate Arrayref runs a build-time payload

https://safedep.io/arrayref-proc-macro1-rust-build-time-malware/
460•abhisek•17h ago•394 comments

I should have loved biology (2020)

https://jsomers.net/i-should-have-loved-biology/
244•tyre•12h ago•91 comments

Ox Alpha

https://openrouter.ai/stealth/ox-alpha
89•mtokmak06•6h ago•73 comments

There's no such thing as a small software team anymore

https://jacob.gold/posts/theres-no-such-thing-as-a-small-software-team/
70•mooreslaw•6h ago•112 comments

Captain Zilog

https://www.zilog.com/captain_zilog/
41•rbanffy•3d ago•4 comments

CIA funding helped keep NeXT afloat in the 80s

https://www.wsj.com/tech/steve-jobs-apple-next-cia-161b65f9?st=NWWds1&reflink=desktopwebshare_per...
386•EwanG•1d ago•232 comments

Why aren't smart people happier? (2022)

https://www.experimental-history.com/p/why-arent-smart-people-happier
143•rafaelc•11h ago•195 comments

AI companies destroy physical books – let's scan rare books before it's too late

https://annas-archive.gl/blog/physical-destruction.html
255•Cider9986•3h ago•175 comments

Show HN: Huzzah – a novel approach to coding with AI

https://www.danielvaughn.dev/posts/huzzah/
279•danielvaughn•11h ago•146 comments

Make a 6-Tesla-class high-temperature superconducting dipole magnet at 4.2 K

https://journals.aps.org/prab/abstract/10.1103/4nhs-bkwh
31•supermagnet•6d ago•5 comments

Japan tried to build an operating system for the world, the US intervened

https://www.xda-developers.com/japan-tried-build-operating-system-entire-world-us-government-inte...
24•rdmuser•1h ago•5 comments

Version Control for Everything

https://tyoverby.com/posts/version-control-for-everything-else/
5•evakhoury•3d ago•0 comments

Vomit: Clean up Claude 5's token output with a separate LLM

https://github.com/zachahn/vomit
230•Bluestein•15h ago•232 comments

Linux 7.2

https://www.igalia.com/2026/08/19/Linux-72-Released.html
228•mariuz•14h ago•77 comments

AliExpress runs silent WebAudio fingerprinting that breaks Bluetooth multipoint

https://blog.laserphile.com/2026/08/aliexpress-webpage-keeping-multipoint.html
942•emctech•20h ago•297 comments

Speeding Up (Small) Ruby Hashes

https://byroot.github.io/ruby/performance/2026/08/13/speeding-up-ruby-hashes.html
43•arto•1w ago•0 comments

Git at any scale

https://cursor.com/blog/git-at-any-scale
318•meetpateltech•2d ago•102 comments

SpacetimeDB: A Short Technical Review

https://strn.cat/posts/spacetime/
81•hurrrr•11h ago•17 comments

Anti-AI fonts are useless and harmful

https://blog.yaros.ae/anti-ai-fonts-are-useless-and-harmful/
144•speckx•15h ago•101 comments

Stop Anthropomorphizing Intermediate Tokens as Reasoning/Thinking Traces

https://arxiv.org/abs/2504.09762
221•nunodonato•1d ago•135 comments

Consumer Rights Wiki

https://consumerrights.wiki/w/Main_Page
264•gregsadetsky•12h ago•49 comments

Project Cybersyn (2022)

https://bactra.org/notebooks/cybersyn.html
58•cassepipe•12h ago•44 comments

How to compromise your system with a job interview

https://www.codedge.de/posts/how-to-compromise-your-system-with-a-job-interview
149•codedge•14h ago•131 comments

Aaron Swartz was prosecuted for scraping, while Meta does it without consequence

https://blog.curiousquail.com/im-upset-again-about-a-co-creator-of-rss-being-prosecuted-for-somet...
1356•speckx•10h ago•294 comments

Every Model Cheats

https://dreadnode.io/research/every-model-cheats-prompt-level-mitigation-of-cheating-on-offensive...
94•vga805•16h ago•76 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.