frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Qwen 3.8 27B

https://huggingface.co/Qwen/Qwen3.8-27B-FP8
793•erdaltoprak•8h ago•520 comments

Going Dark, and the era of law enforcement hacking

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

RISC-V: They should have known better

https://dmitry.gr/?r=06.%20Thoughts&proj=12.%20RV
8•kaycebasques•30m ago•0 comments

Why does Opus 5 feel worse to work with?

https://mun-logadan.github.io/why-does-opus-5-feel-worse/
722•numeri•12h ago•659 comments

RustDesk now supports true unattended remote access on Wayland

https://rustdesk.com/blog/unattended-remote-access-wayland/
195•rustdesk•6h ago•88 comments

Google is making private AI practical with homomorphic encryption

https://blog.google/security/how-google-is-making-private-ai-practical-with-homomorphic-encryption/
235•u1hcw9nx•7h ago•143 comments

Super Mario Derivations

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

AI by Hand

https://www.byhand.ai/
165•sans_souse•7h ago•14 comments

Introducing Toast 1

https://www.mixedbread.com/blog/toast-1
169•mplappert•8h ago•57 comments

New Lower and Upper Bounds for the Grothendieck Constant

https://arxiv.org/abs/2608.11158
24•surprisetalk•3h ago•4 comments

Ultraviolet Bird Photography

https://uvbirds.com/
91•EndXA•1w ago•19 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/
128•speckx•8h ago•56 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...
205•DemiGuru•4h ago•52 comments

Show HN: Mole – Deep research agent for your terminal

https://github.com/lajosdeme/mole
36•lajosdeme•4h ago•6 comments

Maximizing the value of your Claude Code sessions

https://claude.com/blog/maximizing-the-value-of-your-claude-code-sessions
111•twapi•6h ago•77 comments

ICTP Announces 2026 Dirac Medal Recipients (Physics)

https://www.ictp.it/news/2026/8/ictp-announces-2026-dirac-medal-recipients
10•rramadass•4d ago•1 comments

Turbo Pascal on CP/M, MSX-DOS and MS-DOS

http://pascal.hansotten.com/delphi/turbo-pascal-on-cpm-msx-dos-and-ms-dos/
59•rbanffy•2d ago•19 comments

Seven books I keep close because I love them

https://blog.plover.com/2026/08/02/
282•surprisetalk•8h ago•127 comments

Show HN: Ember – Redshift safe color palettes

https://github.com/carpdiem/ember
44•carpdiem•5d ago•7 comments

Don't classify, hallucinate

https://softwaredoug.com/blog/2026/08/10/hypothetical-classifications
212•softwaredoug•4d ago•82 comments

The American sports plutocracy

https://www.derekthompson.org/p/the-american-sports-plutocracy-is
36•momentmaker•4h ago•21 comments

Show HN: LuaCAD – Parametric CAD Scripted in Lua

https://luacad.ad-si.com
62•adius•6h ago•13 comments

GLM-5.3: Frontier coding with emergent cyber capabilities

https://z.ai/blog/glm-5.3
1016•pella•17h ago•501 comments

Every Fucking Website (2020)

https://lxe.github.io/everywebsite/
702•doubletwoyou•8h ago•392 comments

A humble cabbage became one of the Forbidden City’s treasures (2025)

https://www.cnn.com/2025/11/10/style/jadeite-cabbage-taiwan-forbidden-city-curio-hnk-intl
51•dude250711•2d ago•7 comments

Open WireGuard Endpoints

https://proxylity.com/articles/now-available-open-wireguard-endpoints-and-async-lambda.html
20•mlhpdx•4h ago•2 comments

Moving integer division to floating-point is trivial

http://marc-b-reynolds.github.io/math/2026/08/10/IntDivByFP.html
29•matt_d•3d ago•12 comments

Every exterior shot in The Taking of Pelham 123

https://iafisher.com/2026/07/pelham-123
18•evakhoury•2h ago•4 comments

Soup Raiders goes native: What you gain by building your own game engine

https://eliasfarhan.ch/gamedev/cpp/2026/08/14/srnative-01-why-a-custom-engine.html
47•kwakwa_cat•3h ago•47 comments

A Contract-Grade Verifier for LLM-Generated GPU Kernels

https://arxiv.org/abs/2608.12700
29•Jimmc414•6h ago•0 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.