frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

PC Gamer recommends RSS readers in a 37mb article that just keeps downloading

https://stuartbreckenridge.net/2026-03-19-pc-gamer-recommends-rss-readers-in-a-37mb-article/
501•JumpCrisscross•12h ago•247 comments

Tin Can, a 'landline' for kids

https://www.businessinsider.com/tin-can-landline-kids-cellphone-cell-alternative-how-2025-9
94•tejohnso•2d ago•70 comments

Can you get root with only a cigarette lighter? (2024)

https://www.da.vidbuchanan.co.uk/blog/dram-emfi.html
22•HeliumHydride•2d ago•1 comments

The gold standard of optimization: A look under the hood of RollerCoaster Tycoon

https://larstofus.com/2026/03/22/the-gold-standard-of-optimization-a-look-under-the-hood-of-rolle...
329•mariuz•12h ago•95 comments

The future of version control

https://bramcohen.com/p/manyana
492•c17r•15h ago•273 comments

Reports of code's death are greatly exaggerated

https://stevekrouse.com/precision
361•stevekrouse•19h ago•269 comments

Why I love NixOS

https://www.birkey.co/2026-03-22-why-i-love-nixos.html
279•birkey•13h ago•189 comments

The way CTRL-C in Postgres CLI cancels queries is incredibly hack-y

https://neon.com/blog/ctrl-c-in-psql-gives-me-the-heebie-jeebies
12•andrenotgiant•2d ago•0 comments

Project Nomad – Knowledge That Never Goes Offline

https://www.projectnomad.us
412•jensgk•18h ago•141 comments

Flash-MoE: Running a 397B Parameter Model on a Laptop

https://github.com/danveloper/flash-moe
334•mft_•19h ago•113 comments

A Copy-Paste Bug That Broke PSpice AES-256 Encryption

https://jtsylve.blog/post/2026/03/18/PSpice-Encryption-Weakness
30•jtsylve•3d ago•8 comments

GoGoGrandparent (YC S16) is hiring Back end Engineers

https://www.ycombinator.com/companies/gogograndparent/jobs/2vbzAw8-backend-engineer
1•davidchl•3h ago

Windows native app development is a mess

https://domenic.me/windows-native-dev/
397•domenicd•21h ago•379 comments

Intuitions for Tranformer Circuits

https://www.connorjdavis.com/p/intuitions-for-transformer-circuits
46•cjamsonhn•5h ago•3 comments

MAUI Is Coming to Linux

https://avaloniaui.net/blog/maui-avalonia-preview-1
192•DeathArrow•15h ago•99 comments

What Young Workers Are Doing to AI-Proof Themselves

https://www.wsj.com/economy/jobs/ai-jobs-young-people-careers-14282284
117•wallflower•12h ago•187 comments

GrapheneOS will remain usable by anyone without requiring personal information

https://grapheneos.social/@GrapheneOS/116261301913660830
341•nothrowaways•9h ago•92 comments

Five Years of Running a Systems Reading Group at Microsoft

https://armaansood.com/posts/systems-reading-group/
151•Foe•13h ago•43 comments

Migrating the American Express Payment Network, Twice

https://americanexpress.io/migrating-the-payments-network-twice/
64•madflojo•6h ago•17 comments

LLMs predict my coffee

https://dynomight.net/coffee/
108•surprisetalk•4d ago•46 comments

You are not your job

https://jry.io/writing/you-are-not-your-job/
128•jryio•15h ago•141 comments

Building an FPGA 3dfx Voodoo with Modern RTL Tools

https://noquiche.fyi/voodoo
181•fayalalebrun•17h ago•40 comments

They're Vibe-Coding Spam Now

https://tedium.co/2026/02/25/vibe-coded-email-spam/
72•raybb•8h ago•44 comments

First and Lego Education Partnership Update

https://community.firstinspires.org/first-lego-education-partnership-update
39•jchin•3d ago•14 comments

More common mistakes to avoid when creating system architecture diagrams

https://www.ilograph.com/blog/posts/more-common-diagram-mistakes/
171•billyp-rva•19h ago•55 comments

I Reverse-Engineered the TiinyAI Pocket Lab from Marketing Photos

https://bay41.com/posts/tiiny-ai-pocket-lab-review/
69•davidklemke•4d ago•20 comments

"Collaboration" Is Bullshit

https://www.joanwestenberg.com/collaboration-is-bullshit/
83•mitchbob•5h ago•31 comments

How to Attract AI Bots to Your Open Source Project

https://nesbitt.io/2026/03/21/how-to-attract-ai-bots-to-your-open-source-project.html
118•zdw•1d ago•18 comments

Ordered Dithering with Arbitrary or Irregular Colour Palettes (2023)

https://matejlou.blog/2023/12/06/ordered-dithering-for-arbitrary-or-irregular-palettes/
22•surprisetalk•5d ago•0 comments

25 Years of Eggs

https://www.john-rush.com/posts/eggs-25-years-20260219.html
274•avyfain•4d ago•74 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•10mo ago

Comments

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