frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Kimi-K3 Releases on HuggingFace 7/27

https://huggingface.co/moonshotai/Kimi-K3
408•nateb2022•5h ago•180 comments

The Birth of the American 12-string Guitar

https://www.harpguitars.net/history/grunewald/12-string.htm
6•bilegeek•28m ago•0 comments

PGSimCity - How PostgreSQL Works

https://nikolays.github.io/PGSimCity/
662•jonbaer•11h ago•66 comments

Show HN: Physically accurate black hole you can put in your room

https://blackhole.plav.in
346•aplavin•3d ago•104 comments

Magnolias Are So Old That They're Pollinated by Beetles, Not Bees

https://mymodernmet.com/magnolia-ancient-flowers-beetles/
59•speckx•4d ago•18 comments

Libsm64: Mario 64 as a library for use in external game engines

https://github.com/libsm64/libsm64
12•klaussilveira•1h ago•2 comments

Chinese chipmaker shares surge 470%

https://www.bbc.com/news/articles/c9q9w3x9qn2o
56•pingou•2h ago•34 comments

Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary

https://github.com/vercel-labs/scriptc
205•maxloh•12h ago•105 comments

VLC for Unity now supported on Linux

https://code.videolan.org/videolan/vlc-unity
14•martz•2h ago•1 comments

French firefighters face 'pyrocumulonimbus' for first time

https://www.france24.com/en/live-news/20260726-french-firefighters-face-pyrocumulonimbus-for-firs...
399•saaaaaam•17h ago•275 comments

Decker, a platform that builds on the legacy of Hypercard and classic macOS

https://beyondloom.com/decker/
324•tosh•16h ago•75 comments

US citizen charged after GrapheneOS phone wipes during airport search

https://www.techspot.com/news/113236-us-prosecutors-charge-atlanta-man-after-grapheneos-phone.html
843•eecc•12h ago•624 comments

We have proof automation now

https://www.imperialviolet.org/2026/07/26/zstd-lean.html
181•zdw•14h ago•69 comments

How Unix spell ran in 64 kB of RAM

https://blog.codingconfessions.com/p/how-unix-spell-ran-in-64kb-ram
39•donw•2h ago•3 comments

Htmx 4.0, the first JavaScript library to release exclusively on the Game Boy

https://swag.htmx.org/en-cad/products/htmx-4-the-game
464•rcy•23h ago•154 comments

Elevated errors on Claude Opus 5

https://status.claude.com/incidents/lhqp09kxq7pb
7•flyaway123•3h ago•2 comments

I wanted a clock that never needed setting. Things escalated

https://arstechnica.com/gadgets/2026/07/i-wanted-a-clock-that-never-needed-setting-things-escalated/
121•lee_ars•3d ago•105 comments

Introduction to Data-Oriented Design [pdf]

https://www.gamedevs.org/uploads/introduction-to-data-oriented-design.pdf
186•tosh•17h ago•51 comments

Shay Locomotives

https://www.shaylocomotives.com/
4•Rygian•1h ago•0 comments

Fonts In Use – Find out where a font is used

https://fontsinuse.com/
79•open_•11h ago•9 comments

Measuring developer productivity with the DX Core 4

https://getdx.com/research/measuring-developer-productivity-with-the-dx-core-4/
22•saikatsg•3d ago•16 comments

Modern email can be built from borrowed parts

https://en.andros.dev/blog/d7ed8b07/modern-email-can-be-built-from-borrowed-parts/
5•andros•2h ago•2 comments

Boox Go 10.3 (gen II) Lumi: First impressions

https://manualdousuario.net/en/boox-go-10-3-lumi-first-impressions/
11•rpgbr•4d ago•2 comments

Simulate cassette tape audio profiles using FFmpeg

https://github.com/AARomanov1985/Audio-Cassette-Simulation
139•xterminal•15h ago•58 comments

Design is compromise

https://stephango.com/design-is-compromise
263•ankitg12•19h ago•88 comments

The Usefulness of Useless Knowledge (1939) [pdf]

https://faculty.lsu.edu/kharms/files/flexner_1939.pdf
87•jxmorris12•3d ago•4 comments

Show HN: CheapSecurity – Lightweight, Self-Hosted CCTV for Linux SBCs

https://github.com/gmrandazzo/CheapSecurity
131•zeldone•19h ago•27 comments

Show HN: Reverse Minesweeper

https://sunflowersgame.com/
229•pompomsheep•22h ago•79 comments

Go Analysis Framework: modular static analysis by go team

https://pkg.go.dev/golang.org/x/tools/go/analysis
212•AbuAssar•22h ago•74 comments

8086 Emulator Inside Scratch

https://turbowarp.org/1248315967?size=640x400
8•rickcarlino•4d 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.