frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Please Use AI

https://shawnsmucker.substack.com/p/please-use-ai
347•garycomtois•1h ago•92 comments

I Am Retiring from Tech to Live Offline

https://openpath.quest/2026/i-am-retiring-from-tech-to-live-offline/
23•PinkG•19m ago•2 comments

Tulip mania: when a single flower was worth more than a house (2025)

https://dutchreview.com/culture/tulip-mania-netherlands/
78•dotcoma•3h ago•70 comments

The UK Government's Low Value Purchase System Is a Waste of Time

https://shkspr.mobi/blog/2026/05/the-uk-governments-low-value-purchase-system-is-a-waste-of-time/
88•ColinWright•2h ago•46 comments

Bricks and Minifigs Stole a Man's $200k Lego Collection

https://mybricklog.com/blog/bricks-minifigs-corporate-stole-old-mans-200000-lego-collection
1170•philips•19h ago•516 comments

Expertise in the Age of AI

https://www.moderndescartes.com/essays/ai_and_expertise/
14•brilee•1h ago•4 comments

Local Git Remotes

https://cblgh.org/posts/local-git-remotes/
36•surprisetalk•2h ago•26 comments

High Density Living, 2000 Years Ago: Inside the Roman Apartment Building

https://commonedge.org/high-density-living-2000-years-ago-inside-the-roman-apartment-building/
30•surprisetalk•2h ago•8 comments

Real-time LLM Inference on Standard GPUs: 3k tokens/s per request

https://blog.kog.ai/real-time-llm-inference-on-standard-gpus-3-000-tokens-s-per-request/
106•NicoConstant•5h ago•53 comments

Poll: How often do you check "newest"?

16•ColinWright•2h ago•14 comments

Cedana (YC S23) Is Hiring

https://www.ycombinator.com/companies/cedana/jobs/d1vYocG-forward-deployed-engineer-ai-hpc
1•neelm•2h ago

Claude Code – Everything You Can Configure That the Docs Don't Tell You

https://buildingbetter.tech/p/i-read-the-claude-code-source-code
254•ankitg12•12h ago•51 comments

Show HN: AISlop, a CLI for catching AI generated code smells

https://github.com/scanaislop/aislop
57•Heavykenny•1h ago•47 comments

Is This Sustainable?

https://jamiehurst.co.uk/2026-05-24_ai-sustainable
70•ColinEberhardt•4h ago•58 comments

Orchestrating AI code review at scale

https://blog.cloudflare.com/ai-code-review/
74•pramodbiligiri•3d ago•25 comments

I made a million dollar product from my dorm room (2025)

https://nick.winans.io/blog/nice-nano/
498•mattrighetti•18h ago•75 comments

Claude Opus 4.8

https://www.anthropic.com/news/claude-opus-4-8
1657•craigmart•22h ago•1293 comments

An Obsessive Focus on UX: Pilot's Pressure-Regulating Kire-Na Highlighter

https://www.core77.com/posts/143832/An-Obsessive-Focus-on-UX-Pilots-Pressure-Regulating-Kire-Na-H...
30•surprisetalk•3d ago•9 comments

Blue Origin rocket explodes on launchpad in a setback

https://www.reuters.com/science/blue-origin-says-it-faced-anomaly-during-hot-fire-test-2026-05-29/
13•onemoresoop•36m ago•1 comments

Let's compile Quake like it's 1997

https://fabiensanglard.net/compile_like_1997/
119•goranmoomin•11h ago•43 comments

Headway Therapy Patients Forced to Scan Their Faces to Keep Getting Care

https://www.404media.co/headway-therapy-facial-scan-biometric-data-identity-verification/
15•pavel_lishin•44m ago•0 comments

Is AI causing a repeat of Front end's Lost Decade?

https://mastrojs.github.io/blog/2026-05-23-is-AI-causing-a-repeat-of-frontends-lost-decade/
147•xyzal•3h ago•144 comments

Volkswagen blocks Home Assistant by requiring client assertion

https://github.com/robinostlund/homeassistant-volkswagencarnet/issues/967
298•Kwastie•9h ago•150 comments

We should be more tired than the model

https://vickiboykis.com/2026/05/28/we-should-be-more-tired-than-the-model/
70•tosh•2h ago•71 comments

Even (very) noisy LLM evaluators are useful for improving AI agents

https://www.tensorzero.com/blog/even-very-noisy-llm-evaluators-are-useful-for-improving-ai-agents/
11•GabrielBianconi•2d ago•0 comments

HeidiSQL – Lightweight MariaDB, MySQL, SQL Server, PostgreSQL and SQLite Manager

https://github.com/HeidiSQL/HeidiSQL
78•peter_d_sherman•11h ago•30 comments

Italians and Dutch share the same gestural instinct for teaching

https://www.mpi.nl/news/italians-and-dutch-share-same-gestural-instinct-teaching
98•vi_sextus_vi•12h ago•45 comments

Wterm – Terminal Emulator for the Web

https://wterm.dev/
25•m3h•6h ago•3 comments

Show HN: Context-aware Japanese furigana using Sudachi and ModernBERT

https://www.ezfurigana.com/
7•epitrochoid413•2h ago•3 comments

Ten Basic Clouds

https://www.noaa.gov/jetstream/clouds/ten-basic-clouds
168•nopg•4d ago•44 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•1y ago

Comments

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

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•1y 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•1y 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•1y 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.