frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Show HN: To Honor Sir Patrick Stewart, Enjoy the TNG Episode Guessing Game

https://tng.episodle.com/
145•francisofascii•6h ago•42 comments

My favourite PowerMac is a Nintendo Wii

https://virtuallyfun.com/2026/10/29/my-favourite-powermac-is-a-nintendo-wii/
274•DHowett•12h ago•77 comments

Tell HN: Scribd Breached

111•x______________•3h ago•36 comments

Cloudflare Turnstile solver library (no headless browser required)

https://github.com/chris124567/cfsolve
147•costco•2d ago•42 comments

Northflank Breached

https://status.northflank.com
404•js4ever•14h ago•299 comments

OpenAI raises less than half of $30B target

https://www.wsj.com/tech/ai/openai-raises-less-than-half-of-30-billion-target-in-latest-round-91a...
114•timr•2h ago•66 comments

The $6.3B Binance hack was pulled off in just 20 minutes

https://www.wired.com/story/the-dollar63-billion-binance-hack-was-pulled-off-in-just-20-minutes/
391•domhudson•17h ago•267 comments

Breaking the open web won't stop the bad bots

https://www.techpolicy.press/breaking-the-open-web-wont-stop-the-bad-bots/
228•raybb•3d ago•104 comments

Show HN: A working Nintendo in ~1GB of Qwen weights

https://github.com/dbreunig/nesformer
227•dbreunig•13h ago•118 comments

The oldest ice disappears and the Stone Age emerges from it

https://www.sciencenorway.no/archaeology-climate-culture/the-oldest-ice-is-disappearing-the-stone...
123•dxs•10h ago•51 comments

Longitudinal Changes InWearable-Captured PhysiologyBefore Sudden Cardiac Death

https://www.jacc.org/doi/epdf/10.1016/j.jaccas.2026.110397
11•brandonb•2d ago•4 comments

sanstun: A sans-IO, parallel-friendly WireGuard implementation in Rust

https://www.firezone.dev/blog/introducing-sanstun
100•wh33zle•8h ago•17 comments

Infinite Mac: BeOS

https://blog.persistent.info/2026/10/infinite-mac-beos.html
135•ecliptik•10h ago•56 comments

Florilegium: Procedural Flowers in LaTeX

https://github.com/kevinraymond/florilegium
240•nanna•14h ago•44 comments

Flock camera searches fell 95% after a dispatcher's misconduct was caught

https://www.wkyc.com/article/news/investigations/flock-camera-searches-fall-95-percent-highland-h...
66•MilnerRoute•3h ago•6 comments

Brief History of PDP Computers

https://entropicthoughts.com/history-of-pdp-computers
6•ibobev•1d ago•0 comments

The federated code forge

https://tangled.org/blog/forge/
259•zlliang•14h ago•82 comments

Jules Verne's Lost Novel

https://blue-continuum.com/verne-paris
96•dnetesn•10h ago•19 comments

Double Buffering with Cloudflare Queues

https://bellone.com/technical/double-buffering-with-cloudflare-queues
18•b_llc•2d ago•2 comments

Backdoor in Claude Code for VS Code extension on the Cursor Marketplace

https://phorion.io/blog/offical-claude-code-vsx-compromise/
857•_chall•22h ago•512 comments

Azure's Weakest Link – Five Full Cross-Tenant Compromises

https://www.binarysecurity.no/posts/2026/10/one-root-case
291•swq115•19h ago•56 comments

Through Captain Jean-Luc Picard, Patrick Stewart taught us the measure of a man

https://www.bostonglobe.com/2026/10/29/metro/patrick-stewart-picard-star-trek-the-next-generation/
272•apress•9h ago•148 comments

Cisco gives engineer unlimited AI tokens to rewrite legacy code

https://fortune.com/2026/10/30/cisco-president-jeetu-patel-gen-z-27-year-old-unlimited-ai-tokens-...
144•taubek•15h ago•184 comments

Turning a solar power system into its own backup

https://arstechnica.com/science/2026/10/turning-a-solar-power-system-into-its-own-backup/
44•PaulHoule•1d ago•15 comments

Trapped in the Technologist Factory

https://ideolalia.com/essays/trapped-in-the-technologist-factory.html
20•luu•2d ago•7 comments

Building an AI-native engineering org

https://twitter.com/sgondala2/status/2115832070274723875
131•sgondala_ycapp•1d ago•168 comments

Tree-mounted machines connect to web app to let users knock on wood remotely

https://www.designboom.com/technology/tree-mounted-machines-web-app-users-knock-on-wood-remotely/
80•surprisetalk•3d ago•33 comments

Sleep framework: A new way for LLMs to retain knowledge in continual learning

https://research.google/blog/the-sleep-framework-a-new-way-for-llms-to-retain-knowledge-in-contin...
199•acossta•2d ago•22 comments

AI isn't replacing SREs, it's deskilling them

https://newsletter.signoz.io/p/ai-isnt-replacing-sres-its-deskilling
549•dorianniemiec•14h ago•410 comments

Wonderful Weather: Floods and Foreboding in 17th-Century Britain

https://publicdomainreview.org/essay/wonderful-weather/
16•Thevet•2d ago•0 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.