frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Kimi K3 is now live

https://www.kimi.com/en
238•vincent_s•1h ago•121 comments

OnePlus halts operations in USA and Europe

https://community.oneplus.com/thread/2170715118587871237
362•pilililo2•5h ago•194 comments

Goes-19 weather satellite enters Safe Hold mode

https://www.spaceweather.gov/news/goes-19-safe-hold
75•yabones•2h ago•38 comments

How Our Rust-to-Zig Rewrite Is Going

https://rtfeldman.com/rust-to-zig
133•jorangreef•4h ago•30 comments

Let's Build PlanetScale from Scratch: Infrastructure

https://onatm.dev/2026/07/16/homescale-part-1/
81•onatm•4h ago•16 comments

Sony Deletes a Bunch More Movies from the Accounts of People Who 'Bought' Them

https://www.techdirt.com/2026/07/15/sony-deletes-a-bunch-more-movies-from-the-accounts-of-people-...
258•nekusar•3h ago•138 comments

Where are YC founders now? OpenAI and Anthropic, mostly

https://joinedanthropic.com
253•ohong•8h ago•142 comments

Ente – Opening Our Books

https://ente.com/open/
135•Sherex•5h ago•38 comments

Show HN: I've built a words game based on binary search

https://hilogame.cc/
34•ludovicianul•2h ago•28 comments

GC shape stenciling in Go generics

https://rednafi.com/go/gc-shape-stenciling/
7•ingve•4d ago•0 comments

The lost joy of music piracy

https://www.pigeonsandplanes.com/read/music-piracy-what-cd-oink-nine-inch-nails-streaming
601•mcgin•11h ago•400 comments

Guide to data tools landscape for developers

https://sinja.io/blog/data-landscape-guide-for-developers
19•OlegWock•1h ago•2 comments

Inkling: Our Open-Weights Model

https://thinkingmachines.ai/news/introducing-inkling/
1134•vimarsh6739•21h ago•277 comments

How to Train a Gen AI Kick Drum Model on Your Old Linux Desktop with 6GB VRAM

https://www.zhinit.dev/blog/training-a-kick-drum-diffusion-model
6•zhinit•53m ago•1 comments

Accidental Anonymity

https://macwright.com/2026/06/24/accidental-anonymity
18•caminanteblanco•2d ago•2 comments

Teardown: A Generic 7-Port USB 3.0 Hub That Wasn't

https://goughlui.com/2026/07/09/teardown-a-generic-7-port-usb-3-0-hub-that-wasnt/
164•speckx•3d ago•72 comments

1,300 Beautiful Wildlife Illustrations from the 19th Century Now Restored

https://www.openculture.com/2026/07/explore-1300-beautiful-wildlife-illustrations-from-the-19th-c...
189•gslin•12h ago•31 comments

The Act and the Outcome of Creation

https://www.ssp.sh/blog/on-creation/
23•zazuke•4h ago•5 comments

Let's build a simple interpreter for APL – part 1

https://mathspp.com/blog/lsbasi-apl-part1
31•mpweiher•6d ago•0 comments

Track your workout from the iPhone Lock Screen

https://musklr.com/blog/2026/iphone-lock-screen-workout-tracking-live-activity/
30•badgag•5h ago•26 comments

Grok Build is open source

https://github.com/xai-org/grok-build
549•skp1995•19h ago•582 comments

Panel meter calculator with floating point

https://lcamtuf.substack.com/p/panel-meter-calculator-with-floating
28•surprisetalk•3d ago•4 comments

Governments, companies, nonprofits should invest in free, open source AI [pdf]

https://www.siegelendowment.org/wp-content/uploads/2026/07/fortune-david-siegel-open-source-ai.pdf
261•bilsbie•18h ago•94 comments

If you want to create a button from scratch, you must first create the universe

https://madcampos.dev/blog/2026/07/accessibility-from-scratch/
206•treve•12h ago•100 comments

Reynard: A real Firefox web browser for iOS 13 or later

https://github.com/minh-ton/reynard-browser
126•AbuAssar•11h ago•34 comments

Introduction to KizunaShelf: A shelf for everything you love

https://mudkip.me/2026/07/16/Introduction-to-KizunaShelf/
19•mudkipme•3h ago•3 comments

SQLite should have (Rust-style) editions

https://mort.coffee/home/sqlite-editions/
335•gnyeki•17h ago•154 comments

Generative AI Is an Engineering Disaster

https://www.theatlantic.com/technology/2026/07/generative-ai-engineering-disaster/687901/
52•latexr•2h ago•16 comments

World-War-Ⅱ-era telephone line still in use in Upper Tanana Valley Alaska (2021)

https://www.sketchesofalaska.com/2021/03/world-war-ii-era-telephone-line-still.html
16•Lammy•5d ago•2 comments

Making 768 servers look like 1

https://planetscale.com/blog/making-768-servers-look-like-1
131•hisamafahri•12h ago•55 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.