frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Maybe comments should explain 'what' (2017)

https://www.hillelwayne.com/post/what-comments/
68•zahrevsky•2h ago•61 comments

Neural Networks: Zero to Hero

https://karpathy.ai/zero-to-hero.html
437•suioir•8h ago•38 comments

FreeBSD Home NAS, part 3: WireGuard VPN, routing, and Linux peers

https://rtfm.co.ua/en/freebsd-home-nas-part-3-wireguard-vpn-linux-peer-and-routing/
25•todsacerdoti•1h ago•0 comments

JavaScript engines zoo – Compare every JavaScript engine

https://zoo.js.org/
39•gurgunday•2h ago•8 comments

Using AI generated images to get refunds

https://www.wired.com/story/scammers-in-china-are-using-ai-generated-images-to-get-refunds/
31•MattSayar•4d ago•16 comments

The Gentle Seduction (1989)

http://www.skyhunter.com/marcs/GentleSeduction.html
125•JumpCrisscross•4h ago•18 comments

Show HN: I used AI to recreate a $4000 piece of audio hardware as a plugin

30•johnwheeler•1d ago•14 comments

The PGP problem (2019)

https://www.latacora.com/blog/2019/07/16/the-pgp-problem/
24•croemer•4h ago•58 comments

Total monthly number of StackOverflow questions over time

https://data.stackexchange.com/stackoverflow/query/1926661#graph
1240•maartin0•15h ago•695 comments

Was it a billion dollar mistake?

https://www.gingerbill.org/article/2026/01/02/was-it-really-a-billion-dollar-mistake/
17•signa11•2h ago•9 comments

GDI Effects from the PC cracking scene

https://gdimayhem.temari.fr/index.php?p=all
109•todsacerdoti•5d ago•22 comments

The suck is why we're here

https://nik.art/the-suck-is-why-were-here/
338•herbertl•14h ago•190 comments

From silicon to Darude – Sandstorm: breaking famous synthesizer DSPs [video]

https://media.ccc.de/v/39c3-from-silicon-to-darude-sand-storm-breaking-famous-synthesizer-dsps
61•anigbrowl•4d ago•8 comments

Nightshade: Make images unsuitable for model training

https://nightshade.cs.uchicago.edu/whatis.html
4•homebrewer•53m ago•0 comments

Anatomy of BoltzGen

https://huggingface.co/spaces/ludocomito/anatomy-of-boltzgen
15•danielfalbo•2h ago•1 comments

The Most Popular Blogs of Hacker News in 2025

https://refactoringenglish.com/blog/2025-hn-top-5/
610•mtlynch•21h ago•116 comments

Can I start using Wayland in 2026?

https://michael.stapelberg.ch/posts/2026-01-04-wayland-sway-in-2026/
159•secure•5h ago•114 comments

Swift on Android: Full Native App Development Now Possible

https://docs.swifdroid.com/app/
239•mihael•13h ago•136 comments

KDE onboarding is good now

https://rabbitictranslator.com/kde-onboarding/
133•todsacerdoti•12h ago•83 comments

India has surpassed Japan to become the fourth-largest economy

https://www.dw.com/en/india-overtakes-japan-as-4th-largest-economy-report-says/a-75341063
20•guptadeepak•4d ago•2 comments

Gershwin-desktop: OS X-like Desktop Environment based on GNUStep

https://github.com/gershwin-desktop/gershwin-desktop
60•rguiscard•9h ago•14 comments

MyTorch – Minimalist autograd in 450 lines of Python

https://github.com/obround/mytorch
83•iguana2000•12h ago•14 comments

Corroded: Illegal Rust

https://github.com/buyukakyuz/corroded
136•csmantle•12h ago•37 comments

Show HN: Claude Reflect – Auto-turn Claude corrections into project config

https://github.com/BayramAnnakov/claude-reflect
48•Bayram•8h ago•18 comments

How Thomas Mann Wrote the Magic Mountain

https://www.theguardian.com/books/2025/dec/31/the-master-of-contradictions-by-morten-hi-jensen-re...
71•Caiero•11h ago•27 comments

Pixoo Sign Client for Ruby

https://github.com/tenderlove/pixoo-rb
27•0x54MUR41•6h ago•1 comments

Show HN: Replacing my OS process scheduler with an LLM

https://github.com/mprajyothreddy/brainkernel
46•ImPrajyoth•4d ago•28 comments

The Late Arrival of 16-Bit CP/M

https://nemanjatrifunovic.substack.com/p/the-late-arrival-of-16-bit-cpm
58•rbanffy•5d ago•6 comments

The First Video Game Came Long Before Pong

https://www.iflscience.com/the-first-video-game-came-long-before-pong-and-was-invented-by-a-manha...
16•geox•4d ago•3 comments

Ed25519-CLI – command-line interface for the Ed25519 signature system (2024)

https://lib25519.cr.yp.to/ed25519-cli.html
91•INGELRII•6d ago•40 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•7mo ago

Comments

tonyarkles•7mo 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•7mo ago
You can convert edge coloring problems into vertex coloring problems and vice versa through a simple O(n) procedure.
meindnoch•7mo 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•7mo ago
Indeed. Thanks, I stand corrected.
tonyarkles•7mo 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•7mo 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•7mo 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•7mo ago
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•7mo 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•7mo 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•7mo 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.
phkahler•7mo ago
Is this going to lead to faster compile times? Faster register allocation...
john-h-k•7mo ago
Very few compilers actually use vertex coloring for register allocation
isaacimagine•7mo 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•7mo ago
and this post isn't even about vertex coloring
DannyBee•7mo 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.