frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: SQL-tap – Real-time SQL traffic viewer for PostgreSQL and MySQL

https://github.com/mickamy/sql-tap
57•mickamy•3h ago•7 comments

Show HN: I spent 3 years reverse-engineering a 40 yo stock market sim from 1986

https://www.wallstreetraider.com/story.html
167•benstopics•4d ago•37 comments

Understanding the Go Compiler: The Linker

https://internals-for-interns.com/posts/the-go-linker/
38•valyala•5d ago•0 comments

The Three Year Myth

https://green.spacedino.net/the-three-year-myth/
7•surprisetalk•3d ago•0 comments

NPMX – a fast, modern browser for the NPM registry

https://npmx.dev
76•slymax•5h ago•37 comments

Show HN: Data Engineering Book – An open source, community-driven guide

https://github.com/datascale-ai/data_engineering_book/blob/main/README_en.md
138•xx123122•10h ago•11 comments

Cogram (YC W22) – Hiring former technical founders

https://www.ycombinator.com/companies/cogram/jobs/LDTrViN-ex-technical-founder-product-engineer
1•ricwo•38m ago

Backblaze Drive Stats for 2025

https://www.backblaze.com/blog/backblaze-drive-stats-for-2025/
43•Brajeshwar•3h ago•5 comments

GPT-5.2 derives a new result in theoretical physics

https://openai.com/index/new-result-theoretical-physics/
458•davidbarker•12h ago•315 comments

Common Lisp Screenshots: today's CL applications in action

http://www.lisp-screenshots.org
89•_emacsomancer_•2d ago•24 comments

Building a TUI is easy now

https://hatchet.run/blog/tuis-are-easy-now
201•abelanger•13h ago•138 comments

Do Not Outsource Judgement

https://dncrews.com/do-not-outsource-judgement-76f9e5be61b9
12•mawaldne•1h ago•5 comments

Font Rendering from First Principles

https://mccloskeybr.com/articles/font_rendering.html
135•krapp•6d ago•19 comments

Gradient.horse

https://gradient.horse
215•microflash•4d ago•47 comments

Adventures in Neural Rendering

https://interplayoflight.wordpress.com/2026/02/10/adventures-in-neural-rendering/
24•ingve•3d ago•1 comments

The EU moves to kill infinite scrolling

https://www.politico.eu/article/tiktok-meta-facebook-instagram-brussels-kill-infinite-scrolling/
506•danso•10h ago•522 comments

An AI Agent Published a Hit Piece on Me – More Things Have Happened

https://theshamblog.com/an-ai-agent-published-a-hit-piece-on-me-part-2/
366•scottshambaugh•7h ago•183 comments

gRPC: From service definition to wire format

https://kreya.app/blog/grpc-deep-dive/
118•latonz•4d ago•16 comments

Babylon 5 is now free to watch on YouTube

https://cordcuttersnews.com/babylon-5-is-now-free-to-watch-on-youtube/
118•walterbell•22h ago•62 comments

Fix the iOS keyboard before the timer hits zero or I'm switching back to Android

https://ios-countdown.win/
1410•ozzyphantom•17h ago•694 comments

Monosketch

https://monosketch.io/
756•penguin_booze•19h ago•133 comments

Ask HN: Are there examples of 3D printing data onto physical surfaces?

8•catapart•10h ago•9 comments

Faster Than Dijkstra?

https://systemsapproach.org/2026/02/09/faster-than-dijkstra/
121•drbruced•4d ago•71 comments

WolfSSL sucks too, so now what?

https://blog.feld.me/posts/2026/02/wolfssl-sucks-too/
107•thomasjb•21h ago•82 comments

Advanced Aerial Robotics Made Simple

https://www.drehmflight.com
122•jacquesm•5d ago•10 comments

I'm not worried about AI job loss

https://davidoks.blog/p/why-im-not-worried-about-ai-job-loss
238•ezekg•12h ago•403 comments

CSS-Doodle

https://css-doodle.com/
149•dsego•23h ago•16 comments

The wonder of modern drywall

https://www.worksinprogress.news/p/the-wonder-of-modern-drywall
102•jger15•1d ago•162 comments

How did the Maya survive?

https://www.theguardian.com/news/2026/feb/12/apocalypse-no-how-almost-everything-we-thought-we-kn...
122•speckx•17h ago•101 comments

OpenAI has deleted the word 'safely' from its mission

https://theconversation.com/openai-has-deleted-the-word-safely-from-its-mission-and-its-new-struc...
478•DamnInteresting•9h ago•243 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.