frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Shadcn/UI now defaults to Base UI instead of Radix

https://ui.shadcn.com/docs/changelog
120•dabinat•4h ago•36 comments

If you're a button, you have one job

https://unsung.aresluna.org/if-youre-a-button-you-have-one-job/
212•nozzlegear•7h ago•103 comments

Command and Conquer Generals natively ported to macOS, iPhone, iPad using Fable

https://github.com/ammaarreshi/Generals-Mac-iOS-iPad/tree/main
565•asronline•14h ago•230 comments

Web-based cryptography is always snake oil

https://www.devever.net/~hl/webcrypto
13•enz•1h ago•11 comments

Apocketlypse

https://0dd.company/galleries/triumph/1.html
13•scaglio•1h ago•1 comments

Pandoc Lua Filters

https://pandoc.org/lua-filters.html
67•ankitg12•1d ago•2 comments

GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance

https://github.com/openai/codex/issues/30364
270•maille•11h ago•103 comments

Programmers need to start meditating now

https://jacob.gold/posts/programmers-need-to-start-meditating-now/
17•enz•2h ago•7 comments

Megawatts by Microwave

https://computer.rip/2026-07-04-microwave-and-power.html
23•eternauta3k•3h ago•2 comments

Jellyfish can heal wounds in minutes. Scientists want their secrets

https://www.mbl.edu/news/jellyfish-can-heal-wounds-minutes-scientists-want-their-secrets
122•hhs•11h ago•25 comments

Google Books (or similar) all book scans – $200k bounty (2025)

https://software.annas-archive.gl/AnnaArchivist/annas-archive/-/work_items/234
464•Cider9986•16h ago•253 comments

Leaking YouTube creators' private videos

https://javoriuski.com/post/youtube
614•javxfps•16h ago•337 comments

Moby Dick Workout (2022)

https://www.hogbaysoftware.com/posts/moby-dick-workout/
40•helloplanets•5h ago•12 comments

Artful Cats: Feline-Inspired Art and Artifacts

https://www.si.edu/spotlight/art-cats
41•jruohonen•3d ago•4 comments

Is The Economist Always Wrong?

https://economist.com/interactive/finance-and-economics/2026/07/02/is-the-economist-always-wrong
37•andsoitis•3h ago•31 comments

Atomic Force Microscope high-speed video, stainless etching, bacteria, and more

https://www.youtube.com/watch?v=DyIQkqBXhS0
72•mhb•2d ago•7 comments

About the Digital Art

https://www.tricivenola.com/about-the-digital-art/
7•NaOH•3d ago•0 comments

The Log Is the Agent

https://arxiv.org/abs/2605.21997
43•iacguy•6h ago•10 comments

Better Models: Worse Tools

https://lucumr.pocoo.org/2026/7/4/better-models-worse-tools/
173•leemoore•13h ago•58 comments

EV Batteries Are Defying Expectations After Miles

https://www.wsj.com/business/autos/ev-batteries-are-defying-expectations-after-hundreds-of-thousa...
47•apparent•3h ago•41 comments

Return of the Nigerian Prince Redux: Beware Book Club and Book Review Scams (2025)

https://writerbeware.blog/2025/09/19/return-of-the-nigerian-prince-redux-beware-book-club-and-boo...
53•Anon84•9h ago•12 comments

Fast Software, the Best Software

https://craigmod.com/essays/fast_software/
6•ustad•2h ago•0 comments

Zig: All Package Management Functionality Moved from Compiler to Build System

https://ziglang.org/devlog/2026/#2026-06-30
202•tosh•17h ago•64 comments

Meta's Un-Stable Signature

https://hackerfactor.com/blog/index.php?/archives/1098-Metas-Un-Stable-Signature.html
85•ementally•3d ago•12 comments

Potential session/cache leakage between workspace instances or consumer accounts

https://github.com/anthropics/claude-code/issues/74066
297•chatmasta•19h ago•129 comments

sqlite-utils 4.0rc2, mostly written by Claude Fable (for about $149.25)

https://simonwillison.net/2026/Jul/5/sqlite-utils-fable/
42•ognyankulev•3h ago•46 comments

"Beyond the limit": Satellites and mirrors in space pose threat to the night sky

https://www.eso.org/public/news/eso2607/
144•Breadmaker•16h ago•242 comments

My ASN Journey series (2024)

https://www.animmouse.com/p/my-asn-journey/
18•antonalekseev•5h ago•6 comments

What ORMs have taught me: just learn SQL (2014)

https://wozniak.ca/blog/2014/08/03/1/index.html
189•ciconia•4d ago•219 comments

Record-breaking solo rower Kelsey Pfendler arrives in Hawaii

https://www.hawaiinewsnow.com/2026/07/04/record-breaking-solo-rower-kelsey-pfendler-arrives-hawaii/
47•MaysonL•8h ago•5 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.