frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Cloud in a Bottle: making self-hosting accessible to everyone

https://cloudinabottle.org/blog/launch-post
237•zplizzi•4h ago•100 comments

GPT-6 Astra on robot arms

https://openai.robocurve.org/gpt-6-astra/
96•Anon84•2h ago•53 comments

The revolt of the reader

https://bcantrill.dtrace.org/2026/09/05/the-revolt-of-the-reader/
200•chmaynard•7h ago•73 comments

OpenBSD Stories: Strange Medieval Devices

http://miod.online.fr/software/openbsd/stories/smd.html
18•zdw•3d ago•2 comments

Chrome again exempts Google from user site data settings

https://lapcatsoftware.com/articles/2026/9/1.html
187•ExMachina73•5h ago•28 comments

Learn Programming with OCaml

https://usr.lmf.cnrs.fr/lpo/
204•elvis70•11h ago•80 comments

Private German rocket makes history, reaches orbit from European soil

https://www.space.com/space-exploration/launches-spacecraft/isar-aerospace-second-launch-norway-a...
428•bookmtn•8h ago•235 comments

The "$60 Gaming PC" – AMD BC-250 (2025)

https://devquasar.com/hardware/the-60-gaming-pc-amd-bc-250/
311•networked•15h ago•91 comments

The ColorChecker, photography's most important 24 squares, turns 50

https://www.dpreview.com/news/the-colorchecker-photographys-most-important-24-squares-turns-50/
4•sohkamyung•4d ago•0 comments

Discovery of a new OpenAI agent message board

https://collusion.wiki/
2148•moultano•1d ago•1528 comments

RecurseCenter.return()

https://mm-dev.rocks/series/recursecenter.return/
27•evakhoury•4d ago•3 comments

AI, Tools and Transformation

https://www.ben-evans.com/benedictevans/2026/9/3/ai-tools-and-transformation
8•firexcy•2h ago•2 comments

Trump signs order to remove endangered species protection for grey wolves

https://www.bbc.com/news/articles/c62k677d4lzo
17•Alien1Being•54m ago•0 comments

Topologist's Map of the World

https://www.futilitycloset.com/2026/09/01/small-world-20/
56•beardyw•4d ago•18 comments

How Swiss tables work in Go built-in map

https://victoriametrics.com/blog/go-swiss-table-map/index.html
59•valyala•2d ago•4 comments

Visualizing Rust's Vtables: How dyn Trait Works In Memory

https://sofiabelen.github.io/projects/visualizing-rusts-vtables-how-dyn-trait-works-in-memory/
148•torutofu•15h ago•22 comments

Actively exploited sandbox RCE in all Chromium versions

https://nvd.nist.gov/vuln/detail/cve-2026-85046
758•negura•1d ago•448 comments

Nitter has more working instances than before the takedowns

https://codeberg.org/mv12star/shitter/wiki/Instances
652•Cider9986•1d ago•318 comments

Finite time blowup for an averaged three-dimensional Navier-Stokes equation (2014)

https://terrytao.wordpress.com/2014/02/04/finite-time-blowup-for-an-averaged-three-dimensional-na...
64•gmays•8h ago•32 comments

LLMs as a Cognitive Virus

https://arxiv.org/abs/2609.03344
217•canjobear•8h ago•175 comments

Delidded Intel I9-14900KS CT Scan

https://www.lttlabs.com/articles/2026/09/02/delidded-intel-i9-14900ks
83•willx86•3d ago•3 comments

Balrogg: Demonically compacting (up to 15%) lossless Vorbis/Opus recompressor

https://github.com/iczelia/balrogg
71•palaiologos•2d ago•9 comments

Show HN: Fly By – retro biplane flying game

https://michaelteter.com/flyby.html
61•michaelteter•4d ago•42 comments

Terpstra Keyboard

http://terpstrakeyboard.com/
122•cl3misch•18h ago•56 comments

Vancouver strip club's Instagram taken down over sign featuring lake joke

https://www.vancouverisawesome.com/local-news/vancouver-strip-club-instagram-taken-down-sign-call...
7•anigbrowl•33m ago•1 comments

OKF Agent Memory – Git-native persistent memory for AI coding agents

https://github.com/okf-memory/okf-agent-memory
51•okf_memory•6h ago•16 comments

CHC5: Open Camera System – Image Sensor Specification Comparison

https://www.circuitvalley.com/2026/08/chc5-open-camera-sensor-comparison-specification.html
18•devoxel•3d ago•2 comments

ISAR Aerospace 5 Sept Mission Onward and Upward

https://isaraerospace.com/mission-updates-overview
25•t43562•9h ago•4 comments

Statichost.eu – European static site hosting

https://www.statichost.eu/
453•p4bl0•1d ago•205 comments

Can AI design circuit boards yet?

https://eebench.org/blog/can-ai-design-circuit-boards-yet/
395•iopapa•1d ago•209 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.