frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Sizing chaos

https://pudding.cool/2026/02/womens-sizing/
489•zdw•10h ago•256 comments

Martial arts robots at 2026 Spring Festival Gala [video]

https://www.youtube.com/watch?v=mUmlv814aJo
23•lisper•9h ago•11 comments

27-year-old Apple iBooks can connect to Wi-Fi and download official updates

https://old.reddit.com/r/MacOS/comments/1r8900z/macos_which_officially_supports_27_year_old/
304•surprisetalk•11h ago•154 comments

15 years of FP64 segmentation, and why the Blackwell Ultra breaks the pattern

https://nicolasdickenmann.com/blog/the-great-fp64-divide.html
94•fp64enjoyer•6h ago•28 comments

Anthropic officially bans using subscription auth for third party use

https://code.claude.com/docs/en/legal-and-compliance
282•theahura•5h ago•308 comments

Cosmologically Unique IDs

https://jasonfantl.com/posts/Universal-Unique-IDs/
355•jfantl•13h ago•112 comments

Step 3.5 Flash: Fast Enough to Think. Reliable Enough to Act

https://static.stepfun.com/blog/step-3.5-flash/
48•kristianp•5h ago•11 comments

Tailscale Peer Relays is now generally available

https://tailscale.com/blog/peer-relays-ga
390•sz4kerto•15h ago•193 comments

How to choose between Hindley-Milner and bidirectional typing

https://thunderseethe.dev/posts/how-to-choose-between-hm-and-bidir/
84•thunderseethe•3d ago•12 comments

How AI is affecting productivity and jobs in Europe

https://cepr.org/voxeu/columns/how-ai-affecting-productivity-and-jobs-europe
85•pseudolus•7h ago•43 comments

Visualizing the ARM64 Instruction Set (2024)

https://zyedidia.github.io/blog/posts/6-arm64/
19•userbinator•3d ago•1 comments

Stoolap/Node: A Native Node.js Driver That's Surprisingly Fast

https://stoolap.io/blog/2026/02/19/introducing-stoolap-node/
15•murat3ok•1h ago•4 comments

Zero-day CSS: CVE-2026-2441 exists in the wild

https://chromereleases.googleblog.com/2026/02/stable-channel-update-for-desktop_13.html
312•idoxer•15h ago•162 comments

DNS-Persist-01: A New Model for DNS-Based Challenge Validation

https://letsencrypt.org/2026/02/18/dns-persist-01.html
251•todsacerdoti•14h ago•116 comments

Old School Visual Effects: The Cloud Tank (2010)

http://singlemindedmovieblog.blogspot.com/2010/04/old-school-effects-cloud-tank.html
3•exvi•1h ago•0 comments

Minecraft Java is switching from OpenGL to Vulkan

https://www.gamingonlinux.com/2026/02/minecraft-java-is-switching-from-opengl-to-vulkan-for-the-v...
171•tuananh•6h ago•57 comments

A word processor from 1990s for Atari ST/TOS is still supported by enthusiasts

https://tempus-word.de/en/index
26•muzzy19•2d ago•5 comments

A Pokémon of a Different Color

https://matthew.verive.me/blog/color/
99•Risse•3d ago•12 comments

The Perils of ISBN

https://rygoldstein.com/posts/perils-of-isbn
115•evakhoury•14h ago•61 comments

Electrobun v1: Build fast, tiny, and cross-platform desktop apps with TypeScript

https://blackboard.sh/blog/electrobun-v1/
75•merlindru•4h ago•23 comments

All Look Same?

https://alllooksame.com/
60•mirawelner•9h ago•43 comments

Show HN: A Lisp where each function call runs a Docker container

https://github.com/a11ce/docker-lisp
24•a11ce•3h ago•10 comments

R3forth: A concatenative language derived from ColorForth

https://github.com/phreda4/r3/blob/main/doc/r3forth_tutorial.md
82•tosh•12h ago•11 comments

US funding for global internet freedom 'effectively gutted'

https://www.theguardian.com/world/2026/feb/19/us-funding-for-global-internet-freedom-effectively-...
16•xyzal•1h ago•2 comments

Making a font with ligatures to display thirteenth-century monk numerals

https://digitalseams.com/blog/making-a-font-with-9999-ligatures-to-display-thirteenth-century-mon...
79•a7b3fa•3d ago•12 comments

Making the Vortex Mixer

https://www.asimov.press/p/vortex
5•surprisetalk•2d ago•0 comments

Metriport (YC S22) is hiring a security engineer to harden healthcare infra

https://www.ycombinator.com/companies/metriport/jobs/XC2AF8s-senior-security-engineer
1•dgoncharov•11h ago

Show HN: Rebrain.gg – Doom learn, don't doom scroll

81•FailMore•19h ago•28 comments

What Every Experimenter Must Know About Randomization

https://spawn-queue.acm.org/doi/pdf/10.1145/3778029
73•underscoreF•13h ago•43 comments

Show HN: Respectlytics – Open-source, privacy-first mobile analytics (MIT+AGPL)

https://github.com/respectlytics/respectlytics
18•cesncn•3d 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•9mo ago

Comments

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