frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

What Happened to HackerOne?

https://blog.teknogeek.io/posts/what-happened-to-hackerone/
100•hipparchus•2h ago•30 comments

How I use LLMs to learn complex topics

https://laurentiugabriel.github.io/blog/articles/how-i-use-llms-to-learn/
504•laurentiurad•9h ago•286 comments

Turn satellite imagery into a paper globe you fold yourself

https://foldingglobes.com/
19•dango2506•1h ago•3 comments

Show HN: Voice driven murder mystery, Interview AI suspects with your voice

https://www.whodunnitai.com/
8•MrRowTheBoat•1h ago•0 comments

How We Pushed CDC into Postgres

https://www.snowflake.com/en/blog/engineering/postgres-to-snowflake-replication-mirroring/
53•craigkerstiens•3h ago•6 comments

Run Android ARM64 VR APKs on Apple Vision Pro

https://github.com/shinyquagsire23/Klepton
7•LorenDB•1h ago•0 comments

Taxi drivers rarely die of Alzheimer's

https://theconversation.com/taxi-drivers-rarely-die-of-alzheimers-how-complex-mental-maps-and-spa...
223•jader201•13h ago•167 comments

Ask HN: What are you working on? (August 2026)

201•david927•11h ago•725 comments

ATProto for Distributed Systems Engineers

https://atproto.com/articles/atproto-for-distsys-engineers
27•LelouBil•3d ago•3 comments

Picophysics: Single file physics for games on platforms like N64, PSX, DC

https://gitlab.com/Kazade/picophysics
33•klaussilveira•4d ago•8 comments

Tuxedo No. 2 – Cocktail recipes

https://tuxedono2.com
68•smartmic•7h ago•16 comments

Cool URIs Don't Change (1998)

https://www.w3.org/Provider/Style/URI
208•Klaster_1•14h ago•50 comments

"The Persian MâR-Nâmeh Or, the Book for Taking Omens from Snakes" (1892)

https://publicdomainreview.org/collection/marnameh/
43•Thevet•3d ago•5 comments

The tragedy of the commons, AI edition

https://www.economist.com/britain/2026/08/06/the-tragedy-of-the-commons-ai-edition
89•simonpure•8h ago•53 comments

New Zealand lost its music media, and what we're building to replace it

https://propelmusic.co.nz/articles/the-sound-went-quiet-nz-music-media
92•berghoffer•7h ago•54 comments

Andrew Wiles on proving Fermat’s Last Theorem (1995) [video]

https://www.youtube.com/watch?v=GS7CxAtV5Ks
41•jackdoe•3d ago•30 comments

Everything you do is being recorded

https://www.theatlantic.com/technology/2026/05/ai-wearable-surveillance-countermeasures/687203/
240•ike_usawa•17h ago•192 comments

Nearest Pint

https://knowwhereconsulting.co.uk/maps/pubs/
4•bookofjoe•5d ago•0 comments

Japanese court overturns Red RAW video patent

https://www.dpreview.com/news/panasonic-did-what-apple-sony-and-nikon-couldnt-overturn-a-red-raw-...
70•anigbrowl•3h ago•11 comments

OpenChamber: An Agentic Development Environment

https://openchamber.dev/
123•hexomancer•11h ago•69 comments

The German Mittelstand

https://kieranvelasquez.substack.com/p/on-the-german-mittelstand
20•Michelangelo11•3d ago•4 comments

Windows 11's built-in Weather app wastes more than 1 GB of RAM

https://www.notebookcheck.net/Windows-11-s-built-in-Weather-app-wastes-more-than-1-GB-of-RAM.1364...
429•akyuu•13h ago•355 comments

Reviving a four year old reMarkable 2

https://oskrim.github.io/hardware/2026/08/09/remarkable-over-ssh.html
135•oskrim•16h ago•89 comments

Show HN: A Project Oberon System version running on RISC-V instead of RISC-5

https://github.com/rochus-keller/OberonSystem/tree/op2-rv32
109•Rochus•15h ago•16 comments

How Golden Is Silence, Actually?

https://www.newyorker.com/magazine/2026/08/10/silence-kate-mcloughlin-book-review
49•tintinnabula•3d ago•25 comments

The Ambition Project

https://www.betonit.ai/p/the-ambition-project
16•herbertl•5h ago•1 comments

Touring the Consensus, Six Months In

https://theconsensus.dev/blog/2026/08/05/touring-the-consensus-six-months-in.html
18•tosh•3d ago•0 comments

Taylor Farms recalls salsa and guacamole over salmonella risk

https://www.cnbc.com/2026/08/09/taylor-farms-recalls-salsa-and-guacamole-over-salmonella-risk.html
18•cramer4next•2h ago•2 comments

The Alpha 21264 CPU: NT's Greatest RISC (1998)

https://halfhill.com/byte/1998-12_alpha.html
91•Lammy•18h ago•74 comments

Memelang: Token-Terse Query Language

https://memelang.net/11/
9•bri-holt•3d ago•1 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.