frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Kaiser nurses say AI, workplace surveillance are making their jobs, care worse

https://localnewsmatters.org/2026/07/15/kaiser-nurses-say-ai-workplace-surveillance-are-making-th...
447•gnabgib•7h ago•293 comments

Reviving a 15-year-old netbook with Arch Linux

https://parksb.github.io/en/article/41.html
53•parksb•3d ago•26 comments

Regressive JPEGs

https://maurycyz.com/projects/bad_jpeg/
44•vitaut•3h ago•1 comments

AWS: Inaccurate Estimated Billing Data – $1.7 billion

1127•nprateem•20h ago•667 comments

Thanks HN for 15 years of support and helping me find my life's work

498•nicholasjbs•13h ago•50 comments

First atmosphere found on Earth-like planet in habitable zone of distant star

https://www.bbc.com/news/articles/cy4kdd1e0ejo
417•neversaydie•16h ago•253 comments

Moonstone: Modern, cross-platform Lua runtime and package manager written in Zig

https://moonstone.sh/
41•ksymph•5h ago•10 comments

The Zilog Z80 has turned 50

https://goliath32.com/blog/z80.html
197•st_goliath•10h ago•62 comments

TP-Link Kasa cameras leaked home GPS via unauthenticated UDP for 6 years

https://github.com/BadChemical/IoT-Vulnerability-Research-Public/blob/main/TP-Link_Kasa_EC71/Kasa...
86•BadChemical•8h ago•20 comments

I Started a "Dirt Notebook"

https://pinewind.bearblog.dev/i-started-a-dirt-notebook/
42•herbertl•5h ago•31 comments

Learning a few things about running SQLite

https://jvns.ca/blog/2026/07/17/learning-about-running-sqlite/
212•surprisetalk•12h ago•53 comments

The Isomorphic Labs Drug Design Engine unlocks a new frontier beyond AlphaFold

https://www.isomorphiclabs.com/articles/the-isomorphic-labs-drug-design-engine-unlocks-a-new-fron...
64•andsoitis•6h ago•6 comments

Shipping OpenStrike: A Counter-Strike-Shaped FPS on a 2004 Handheld

https://pocketjs.dev/blog/shipping-openstrike/
28•itvision•6d ago•14 comments

Kimi K3, and what we can still learn from the pelican benchmark

https://simonwillison.net/2026/Jul/16/kimi-k3/
309•droidjj•16h ago•166 comments

Stenchill: 3D Printable Solder Paste Stencil Generator

https://www.stenchill.com/en/
30•radeeyate•5h ago•6 comments

Vāgdhenu: A Sanskrit Chanting TTS System

https://prathosh.in/vagdhenu/
126•subinalex•4d ago•25 comments

DrDroid (YC W23) Is Hiring

https://www.ycombinator.com/companies/drdroid/jobs/w45QcNV-product-engineer-assignment-mandatory
1•TheBengaluruGuy•5h ago

Open Book Touch: open-source e-reader

https://www.crowdsupply.com/oddly-specific-objects/open-book-touch
87•surprisetalk•9h ago•27 comments

An Update on Igalia's Layer Based SVG Engine in WebKit (Reducing Layer Overhead)

https://blogs.igalia.com/nzimmermann/posts/2026-07-14-lbse-conditional-layers/
29•bkardell•3d ago•1 comments

Mac gaming is finally getting the overpowered upgrade it deserves

https://www.macworld.com/article/3189951/apples-latest-game-porting-toolkit-beta-changed-how-i-th...
33•kristianp•2h ago•25 comments

Static search trees: 40x faster than binary search (2024)

https://curiouscoding.nl/posts/static-search-tree/
86•lalitmaganti•10h ago•4 comments

In-toto: A framework to secure the integrity of software supply chains

https://in-toto.io/
3•Erenay09•1d ago•0 comments

Lego building instructions through time

https://www.lego.com/en-us/history/articles/d-lego-building-instructions-through-time
95•NaOH•12h ago•20 comments

Painting the sides of railroad rails white to reduce derailment

https://www.up.com/news/safety/Tracking-Rail-Heat-260608
75•zdw•10h ago•41 comments

Battery packs: Let's talk about crates, baby

https://smallcultfollowing.com/babysteps/blog/2026/07/15/battery-packs/
6•MeetingsBrowser•1d ago•2 comments

Show HN: A zoomable timeline of 4M Wikipedia events

https://app.everything.diena.co/
76•lortex•11h ago•30 comments

The state of open source AI

https://stateofopensource.ai/
409•rellem•15h ago•298 comments

Frank Lloyd Wright’s first home

https://www.architecturaldigest.com/story/frank-lloyd-wright-home-and-studio-everything-you-need-...
96•NaOH•5d ago•47 comments

Three ways people respond to a problem (other than solving it)

https://improvesomething.today/responses-to-problems/
224•surprisetalk•16h ago•123 comments

FAA lets Boeing sign off on 737 MAX, 787 airworthiness certificates again

https://www.cnbc.com/2026/07/17/faa-boeing-737-max-787.html
162•hmm37•9h ago•88 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.