frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

15 years later, Microsoft morged my diagram

https://nvie.com/posts/15-years-later/
212•cheeaun•1h ago•63 comments

Halt and Catch Fire: TV's Best Drama You've Probably Never Heard Of (2021)

https://www.sceneandheardnu.com/content/halt-and-catch-fire
354•walterbell•5h ago•189 comments

Terminals should generate the 256-color palette

https://gist.github.com/jake-stewart/0a8ea46159a7da2c808e5be2177e1783
39•tosh•1h ago•8 comments

Claude Sonnet 4.6

https://www.anthropic.com/news/claude-sonnet-4-6
1047•adocomplete•13h ago•919 comments

A DuckDB-based metabase alternative

https://github.com/taleshape-com/shaper
16•wowi42•1h ago•2 comments

Thank HN: You helped save 33k lives

719•chaseadam17•14h ago•75 comments

BarraCUDA Open-source CUDA compiler targeting AMD GPUs

https://github.com/Zaneham/BarraCUDA
261•rurban•11h ago•96 comments

Stardex (YC S21) Is Hiring

https://www.ycombinator.com/companies/stardex/jobs/lag1C1P-customer-success-engineer-ai-data-migr...
1•sanketc•46m ago

Show HN: AsteroidOS 2.0 – Nobody asked, we shipped anyway

https://asteroidos.org/news/2-0-release/index.html
348•moWerk•12h ago•38 comments

Thousands of CEOs just admitted AI had no impact on employment or productivity

https://fortune.com/2026/02/17/ai-productivity-paradox-ceo-study-robert-solow-information-technol...
379•virgildotcodes•6h ago•267 comments

The Economics of a Super Bowl Ad

https://ro.co/perspectives/super-bowl-economics/
25•nnmg•2d ago•22 comments

Gentoo on Codeberg

https://www.gentoo.org/news/2026/02/16/codeberg.html
314•todsacerdoti•14h ago•110 comments

Minimal x86 Kernel Zig

https://github.com/lopespm/zig-minimal-kernel-x86
90•lopespm•7h ago•25 comments

Reverse Engineering Sid Meier's Railroad Tycoon for DOS from 1990

https://www.vogons.org/viewtopic.php?t=105451
69•LowLevelMahn•3d ago•14 comments

Using go fix to modernize Go code

https://go.dev/blog/gofix
326•todsacerdoti•15h ago•69 comments

So you want to build a tunnel

https://practical.engineering/blog/2026/2/17/so-you-want-to-build-a-tunnel
207•crescit_eundo•14h ago•84 comments

Show HN: Beautiful interactive explainers generated with Claude Code

https://paraschopra.github.io/explainers/
16•paraschopra•50m ago•5 comments

Async/Await on the GPU

https://www.vectorware.com/blog/async-await-on-gpu/
185•Philpax•14h ago•50 comments

'My Words Are Like an Uncontrollable Dog': On Life with Nonfluent Aphasia (2025)

https://thereader.mitpress.mit.edu/my-words-are-like-an-uncontrollable-dog-on-life-with-nonfluent...
51•anarbadalov•8h ago•11 comments

Show HN: Breadboard – a modern HyperCard for building web apps on the canvas

https://breadboards.io/
7•simquat•1d ago•0 comments

Semantic Diffusion (2006)

https://martinfowler.com/bliki/SemanticDiffusion.html
3•andsoitis•2d ago•0 comments

TinyIce: Single-binary Icecast2-compatible server (auto-HTTPS, multi-tenant)

https://github.com/DatanoiseTV/tinyice
4•sylwester•1h ago•1 comments

Show HN: I wrote a technical history book on Lisp

https://berksoft.ca/gol/
194•cdegroot•16h ago•73 comments

Use Microsoft Office Shortcuts in Libre Office

https://github.com/Zaki101Aslam/MS-office-shortcuts-for-Libre-Office
43•Zaki101Aslam•3d ago•9 comments

Automatia and the Case for Vanilla

https://fwsgonzo.medium.com/automatia-and-the-case-for-vanilla-b3209cdf1583
5•fwsgonzo•3d ago•0 comments

I converted 2D conventional flight tracking into 3D

https://aeris.edbn.me/?city=SFO
245•kewonit•17h ago•48 comments

Quamina and Claude, Case 1

https://www.tbray.org/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1
16•zdw•3d ago•2 comments

HackMyClaw

https://hackmyclaw.com/
294•hentrep•14h ago•147 comments

Assistant to the Regional Manager

https://smallpotatoes.paulbloom.net/p/assistant-to-the-regional-manager
90•NaOH•4d ago•34 comments

Google Public CA is down

https://status.pki.goog/incidents/5oJEbcU3ZfMfySTSXXd3
239•aloknnikhil•6h ago•134 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.