frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Android 17 is the first since 3.x to add new APIs without releasing to the AOSP

https://grapheneos.social/@GrapheneOS/117282080803799576
651•theanonymousone•9h ago•318 comments

Science Is Open Software

https://jepedersen.dk/blog/202505_research/
31•jegp•1h ago•15 comments

SDCC – Small Device C Compiler

https://sdcc.sourceforge.net/
21•lioeters•1h ago•4 comments

Cloudflare Quick Tunnels

https://try.cloudflare.com/
630•jcbhmr•14h ago•262 comments

Saving another 100TB of RAM

https://blog.cloudflare.com/saving-100-tb-of-ram-with-math/
272•f311a•9h ago•56 comments

How to Write with an LLM

https://sockpuppet.org/blog/2026/09/17/how-to-write-with-an-llm/
431•joeriddles•1d ago•291 comments

Why building a Rust LSP is hard

https://rust-glancer.github.io/blog/why-lsp-is-hard/
21•agluszak•2d ago•9 comments

Show HN: LiveWorld – Every 24/7 YouTube live camera on one globe

https://liveworld.info/
25•harisingh1612•3h ago•27 comments

Xcode 27.1 Beta Release Notes

https://developer.apple.com/documentation/xcode-release-notes/xcode-27_1-release-notes
123•CameronBanga•9h ago•75 comments

The first new cat species discovered in 100 years

https://www.nationalgeographic.com/animals/article/meet-the-first-new-cat-species-discovered-in-1...
206•ohjeez•1d ago•77 comments

How OpenAI Used Its Own LLMs to Design Its Jalapeño Chip

https://spectrum.ieee.org/llms-for-chip-design
75•maxall4•5h ago•66 comments

Photon-Emission-Guided Laser Fault Injection Enables RP2350 Secure Debug

https://donjon.ledger.com/blog/rp2350-secure-debug-laser-fault-injection/
167•synack•11h ago•61 comments

Show HN: Cactus Needle 3: 8-29MB automation models can match DeepSeek V4 Flash

https://cactuscompute.com/needle
175•HenryNdubuaku•1d ago•79 comments

The Farnese letter

https://simonklee.dk/farnese-letter
33•grigolin•1d ago•5 comments

OpenJev

https://openjev.com/
578•ilreb•18h ago•249 comments

Cache-to-Cache: Direct Semantic Communication Between LLMs (2025)

https://arxiv.org/abs/2510.03215
74•rochansinha•9h ago•12 comments

LispBM is a concurrent Lisp for microcontrollers with message passing

https://www.lispbm.com/
18•so-cal-schemer•2d ago•2 comments

Claude Code now reads AGENTS.md if there is no Claude.md

https://code.claude.com/docs/en/changelog
564•datadrivenangel•7h ago•203 comments

Goroutine Leak Profiles

https://go.dev/blog/goroutine-leak-profiles
7•torutofu•2d ago•0 comments

Cyclomatic Complexity in C#

https://blog.ndepend.com/understanding-cyclomatic-complexity/
41•gone35•2d ago•15 comments

Minimal Phone 2

https://minimalcompany.com/
213•nashashmi•1d ago•196 comments

Warez: The Infrastructure and Aesthetics of Piracy (2021)

https://archive.org/details/b904a8eb-9c98-4bb1-bf25-3cb9d075b157
121•succinct_ideas•1d ago•37 comments

Alibaba open-sources AI model that can detect cancer and nearly 150 conditions

https://www.scmp.com/tech/big-tech/article/3368055/alibaba-open-sources-medical-ai-model-can-dete...
64•yogthos•4h ago•8 comments

How SpaceX streamlined the Raptor engine

https://www.construction-physics.com/p/how-spacex-streamlined-the-raptor
181•JumpCrisscross•1d ago•50 comments

Inside ZCode: Silently uploading your Git history to the cloud

https://blog.ferstar.org/en/posts/zcode-silent-workspace-snapshot-upload/
270•csmantle•22h ago•94 comments

C++26: Trivial infinite loops are no longer undefined behaviour

https://www.sandordargo.com/blog/2026/09/16/cpp26-trivial-infinite-loops
154•ibobev•1d ago•212 comments

Two parallel neural ectoderm progenitors contribute to the developing brain

https://www.newscientist.com/article/2589739-our-brain-evolved-from-two-primitive-nervous-systems...
107•Jimmc414•13h ago•60 comments

The Implications of Linguistic Illegibility for LLM Security

https://arxiv.org/abs/2609.02852
57•tomjakubowski•9h ago•21 comments

Size-Specialized Memory Allocation

https://go.dev/blog/size-specialized-allocations
25•spacey•2d ago•3 comments

A search-and-inference database from scratch in pure Zig

https://antfly.io/research/antfly-zig
55•kingcauchy•3d ago•17 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.