frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

The other Sean Byrne doesn't exist

https://conic.al/writing/the-other-sean-byrne-doesnt-exist/
191•rdl•7h ago•101 comments

Qwen 3.8 27B

https://huggingface.co/Qwen/Qwen3.8-27B-FP8
1172•erdaltoprak•20h ago•706 comments

Using GCC's Nested Functions with Wide Pointers and No Trampolines II

https://uecker.codeberg.page/2026-07-14.html
22•uecker•3h ago•1 comments

The mathematical beauty of hyperbezier curves

https://linebender.org/blog/hyperbezier/
15•raphlinus•5d ago•0 comments

Going Dark, and the era of law enforcement hacking

https://blog.cryptographyengineering.com/2026/08/14/everything-is-about-to-go-dark/
352•vslira•14h ago•159 comments

Show HN: Eigendrum - Draw any shape and hear what it sounds like as a drum

https://baselashraf81.github.io/eigendrum/
26•BaselAshraf81•4d ago•5 comments

In 1962, Egypt's Missile Program Lost Its Key Scientist Without a Trace

https://www.popularmechanics.com/military/a73358518/nazi-rocket-scientist-disappearance/
49•bookofjoe•2d ago•22 comments

Understanding WCAG 2.2 as ePub and PDF

https://doeken.org/wcag-ebook
22•doekenorg•2d ago•2 comments

Coin-sized device can hack a Boeing 737

https://www.wired.com/story/this-coin-sized-device-can-hack-a-boeing-737/
88•_tk_•2d ago•59 comments

Google is making private AI practical with homomorphic encryption

https://blog.google/security/how-google-is-making-private-ai-practical-with-homomorphic-encryption/
406•u1hcw9nx•19h ago•247 comments

Show HN: ThoughtDAG – An editable context graph for LLM conversations

https://chenxiachan.github.io/thoughtdag/
45•chatchan•6h ago•12 comments

Firefox is now the last major browser that still supports uBlock Origin

https://www.pcworld.com/article/3212428/firefox-is-now-the-last-major-browser-that-still-supports...
1119•DemiGuru•16h ago•413 comments

Magnitude 7.7 Earthquake – 68 km NNW of Ende, Indonesia

https://earthquake.usgs.gov/earthquakes/eventpage/us6000tkt2/executive
200•Bender•10h ago•48 comments

RustDesk now supports true unattended remote access on Wayland

https://rustdesk.com/blog/unattended-remote-access-wayland/
302•rustdesk•19h ago•128 comments

AI by Hand

https://www.byhand.ai/
315•sans_souse•19h ago•23 comments

eigendrum

https://eigendrum.com/#p=circle
166•bookofjoe•13h ago•45 comments

Show HN: Silent Shark – tactical map-based WWII submarine sim

https://silentshark.app/
34•epaga•2d ago•13 comments

Maximizing the value of your Claude Code sessions

https://claude.com/blog/maximizing-the-value-of-your-claude-code-sessions
237•twapi•19h ago•130 comments

Simplifying and Refactoring Introductory Calculus (2018)

https://arxiv.org/abs/1811.03459
96•E-Reverance•11h ago•48 comments

Unearthing a 31 year old Easter egg in Ecco the Dolphin

https://32bits.substack.com/p/under-the-microscope-ecco-the-dolphin-98c
92•bbayles•2d ago•19 comments

This Hi-Fi Tape Recorder Changed Radio Forever

https://spectrum.ieee.org/magnetophon-laugh-track
50•Jimmc414•3d ago•15 comments

Introducing Toast 1

https://www.mixedbread.com/blog/toast-1
207•mplappert•20h ago•63 comments

Super Mario Derivations

https://fzakaria.com/2026/08/05/super-mario-derivations
110•domenkozar•1w ago•15 comments

I turned my RSS feeds into an e-ink newspaper to stop reading on my phone

https://heyjonny.dev/posts/rss-to-eink-newspaper/
193•speckx•20h ago•77 comments

GLM-5.3: Frontier coding with emergent cyber capabilities

https://z.ai/blog/glm-5.3
1099•pella•1d ago•543 comments

Suspecting court of using AI, man injected prompts in filings to try to win case

https://arstechnica.com/tech-policy/2026/08/suspecting-court-of-using-ai-man-injected-prompts-in-...
36•jnord•3h ago•27 comments

Racket v9.3

https://blog.racket-lang.org/2026/08/racket-v9-3.html
97•privong•17h ago•6 comments

Ultraviolet Bird Photography

https://uvbirds.com/
149•EndXA•1w ago•25 comments

Debian has begun voting on the future of AI/LLM contributions

https://lists.debian.org/debian-devel-announce/2026/08/msg00002.html
13•matheusmoreira•2h ago•8 comments

Why does Opus 5 feel worse to work with?

https://mun-logadan.github.io/why-does-opus-5-feel-worse/
883•numeri•1d ago•798 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.