frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Meta VR Glasses

https://www.meta.com/vr-glasses/
124•polymorph1sm•58m ago•70 comments

Linux support is coming to Snapdragon X2 Series

https://www.qualcomm.com/news/onq/2026/09/snapdragon-summit-agentic-ai-pcs-linux
99•aaronday•2h ago•46 comments

Claude discovers a novel enzyme system with CRISPR-like repeats

https://www.anthropic.com/news/claude-discovers-novel-enzyme-system
463•raahelb•6h ago•506 comments

VSCode's SSH Agent Is Bananas (2025)

https://fly.io/blog/vscode-ssh-wtf/
108•Rapzid•3h ago•74 comments

ArXiv receives multiyear commitments to support it as an independent nonprofit

https://blog.arxiv.org/2026/09/23/arxiv-receives-multiyear-investment/
38•JohnHammersley•2h ago•4 comments

We just shipped support for the ugliest part of HTTP: Vary

https://blog.cloudflare.com/vary-support/
53•thisisfatih•2h ago•6 comments

The "Windows XP Box" (2003)

https://www.mini-itx.com/projects/windowsxpbox/
28•doubletwoyou•1d ago•3 comments

Mercury 2.5 LLM hits 770 tokens per second

https://artificialanalysis.ai/models/mercury-2-5
34•Retro_Dev•2h ago•12 comments

Fixing the Portobello Police Station Clock

https://pointinthecloud.com/2026-04-11-211700.html
375•avidly•9h ago•85 comments

LensVLM: Compressing long context as images, expanding only relevant pages

https://huggingface.co/apple/LensVLM-9B
49•victormustar•6h ago•6 comments

Italian parliament votes for return to nuclear energy

https://apnews.com/article/italy-nuclear-chernobyl-4891b6b7c7791ae84db6b0bf0f7cf567
571•geox•7h ago•362 comments

The mystery animal on an ancient god's head

https://signoregalilei.com/2026/09/13/the-mystery-animal-on-an-ancient-gods-head/
46•surprisetalk•1d ago•14 comments

A brief history of Windows scroll bar shortcuts

https://devblogs.microsoft.com/oldnewthing/20260922-00/?p=112719/
107•tybulewicz•6h ago•47 comments

Gemini 3.8 text-to-speech

https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-3-8-text-to-speech/
248•swolpers•9h ago•118 comments

The Curious Power of Punctuation

https://www.newyorker.com/magazine/2026/09/28/on-the-mark-louis-menand-book-review
19•pepys•1d ago•3 comments

Making Tailscale Faster

https://tailscale.com/blog/making-tailscale-faster
54•yarapavan•6h ago•18 comments

Radicle: Disclosure of Vulnerability in the Network Protocol

https://radicle.dev/2026/09/23/disclosure-of-vulnerability-in-network-protocol
119•lostmsu•9h ago•45 comments

Tokens too cheap to meter

https://jyn.dev/tokens-too-cheap-to-meter/
227•teoruiz•15h ago•178 comments

A refined phylochronology of the second plague pandemic in Western Eurasia

https://www.pnas.org/doi/10.1073/pnas.2534899123
11•Thevet•3d ago•0 comments

I don't want the details

https://michaelheap.com/i-dont-want-the-details/
343•mooreds•11h ago•193 comments

Z80 REPL (2018)

https://abagames.github.io/z80-repl/index.html
143•adunk•13h ago•18 comments

Claude Code reads AGENTS.md only when telemetry is on [fixed]

https://blog.szypowi.cz/p/claude-code-reads-agents.md-only-when-telemetry-is-on/
445•pszypowicz•12h ago•253 comments

Swap, ZRAM, Zswap and Hibernate on NixOS

https://blog.matthewbrunelle.com/swap-zram-zswap-and-hibernate-on-nixos/
29•speckx•6h ago•6 comments

Show HN: I built a post-mortem debugger for native Windows x64/x86 crashes

https://www.forensicdbg.com
24•Loren_SL•5h ago•4 comments

28% of job postings on company career sites have been open over 90 days

https://unlisted.careers/ghost-jobs/report/2026-09
226•rubatrejo•8h ago•293 comments

Once Claude can measure something, it can make it faster

https://claude.dev/blog/how-we-made-claude-ai-faster/
156•matthieu_bl•5h ago•96 comments

Seattle City Council votes to ban surveillance pricing in sale of groceries

https://advocacy.consumerreports.org/press_release/seattle-city-council-votes-to-ban-surveillance...
301•ortusdux•10h ago•190 comments

GPT-6 Sol and Luna

https://openai.com/index/introducing-gpt-6-sol-and-luna/
1730•OfficialTurkey•1d ago•822 comments

QuestDB (YC S20) Is Hiring a Sales Engineer

https://questdb.com/careers/pre-sales-engineer-north-america/
1•nhourcard•12h ago

Stripe's Knowledge AI Platform

https://stripe.dev/blog/meet-stripes-knowledge-ai-platform
172•ltononro•11h ago•108 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.