frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Zig Creator Calls Spade a Spade, Anthropic Blows Smoke

https://raymyers.org/post/zed-creator-calls-spade-a-spade/
178•crowdhailer•1h ago•101 comments

Interrail: 6,379Km and 13 Countries over 7 weeks

https://shkspr.mobi/blog/2026/07/another-ridiculous-interrail-holiday-6379km-and-13-countries-ove...
50•coinfused•2h ago•39 comments

The social physics of conversation: Communication patterns matter

https://andiroberts.com/citizenship/the-social-physics-of-conversation-citizenship-leadership
41•kiyanwang•5d ago•6 comments

GhostLock, a stack-UAF that has existed in all Linux distributions for 15 years

https://nebusec.ai/research/ionstack-part-2/
272•ranger_danger•4d ago•114 comments

Beavis Ultrasound PnP ISA Sound Card Replica

https://github.com/schlae/BeavisUltrasound
61•mariuz•4h ago•21 comments

Cyberpunk Comics, Manga and Graphic Novels

https://shellzine.net/cyberpunk-comics/
190•zdw•11h ago•64 comments

Tiny Emulators

https://floooh.github.io/tiny8bit-preview/index.html
257•naves•13h ago•22 comments

The Graph That Should Be Front-Page News

https://www.lyrebirddreaming.com/post/the-graph-that-should-be-front-page-news
58•rakel_rakel•4h ago•23 comments

Frieve Vinyl Explained – Microscopic stylus/groove physics simulation

https://frieve-a.github.io/sound_toolbox/vinyl_explained/vinyl_explained.html
14•XzetaU8•3d ago•1 comments

So you want to learn physics (second edition, 2021)

https://www.susanrigetti.com/physics
225•azhenley•5d ago•40 comments

Backtrack-Free Cursive

https://mmapped.blog/posts/52-backtrack-free-cursive
86•dmit•4h ago•40 comments

Designing and assembling my first PCB

https://vilkeliskis.com/b/2026/0711.html
113•tadasv•11h ago•51 comments

Guy took Jupiter photo with Game Boy Camera, giant telescope, publishes tutorial

https://www.engadget.com/2211886/guy-who-took-photo-of-jupiter-with-a-game-boy-camera-and-giant-t...
51•thunderbong•2d ago•23 comments

How to read more books

https://scotto.me/blog/2026-07-12-how-to-read-more-books/
370•silcoon•18h ago•195 comments

Ask HN: Add flag for AI-generated articles

684•levkk•8h ago•310 comments

Ask HN: What Are You Working On? (July 2026)

160•david927•12h ago•508 comments

Berkshire's $397B Bet Against an Overheated Market

https://www.disruptionbanking.com/2026/07/13/inside-berkshires-397-billion-bet-against-an-overhea...
28•emsidisii•1h ago•15 comments

Are you telling me a readonly property is wrecking my performance?

https://shub.club/writings/2026/july/check-your-scrollheight/
38•forthwall•3d ago•17 comments

Sam Neill has died

https://www.theguardian.com/film/2026/jul/13/sam-neill-death-actor-dies-aged-78
148•j4mie•4h ago•36 comments

LARP – Revenue infrastructure for serious founders

https://www.larp.website/
244•BerislavLopac•17h ago•50 comments

Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper

https://ploy.ai/blog/migrating-a-production-ai-agent-to-gpt-5-6
210•brryant•17h ago•88 comments

The console wars have been lost

https://xeiaso.net/notes/2026/console-wars-lost/
6•ExMachina73•3d ago•0 comments

Vint Cerf, “father of the Internet”, is retiring

https://techcrunch.com/2026/06/30/the-father-of-the-internet-is-finally-retiring/
316•compiler-guy•3d ago•180 comments

Kode Dot Programmable pocket device for makers, pentesters and geeks

https://kode.diy
84•iNic•12h ago•21 comments

Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k

https://systima.ai/blog/claude-code-vs-opencode-token-overhead
594•systima•15h ago•323 comments

First look at Quest, the final ship of Antarctic explorer Shackleton

https://www.cbc.ca/news/canada/quest-shipwreck-expedition-images-9.7262229
34•curmudgeon22•4d ago•3 comments

Quadrupling code performance with a "useless" if

https://purplesyringa.moe/blog/quadrupling-code-performance-with-a-useless-if/
58•birdculture•2h ago•8 comments

I Learned to Read Again

https://substack.magazinenongrata.com/p/how-i-learned-to-read-again
150•georgex7•15h ago•58 comments

Why write code in 2026

https://softwaredoug.com/blog/2026/07/09/write-code
163•softwaredoug•2d ago•216 comments

How we can reduce traffic congestion

https://research.google/blog/the-power-of-collaboration-how-we-can-reduce-traffic-congestion/
134•raahelb•18h ago•199 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.