frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Roku developer repositories moved from GitHub to GitLab

https://blog.roku.com/developer/gitlab-move
171•cxr•3h ago•112 comments

Dream-1

https://dreamlabs.ai/research/dream-1/
54•GaggiX•1h ago•28 comments

The St. Helena 5 pence coin shows Jonathan, a roughly 190 year old tortoise

https://de.numista.com/9866
60•schleck8•2h ago•10 comments

FreeDNS

https://freedns.afraid.org/
178•esher•4h ago•45 comments

Glymphatic clearance to alleviate traumatic brain edema& Alzheimer's pathology

https://www.science.org/doi/10.1126/sciadv.aeh8870
16•ersinesen•1h ago•5 comments

Neural chip decodes interactions between brain regions

https://actu.epfl.ch/news/neural-chip-decodes-interactions-between-brain-r-2/
60•giuliomagnifico•3h ago•11 comments

Why is AI generated language so hard to understand?

https://arxiv.org/abs/2610.29162
20•canjobear•1h ago•10 comments

John Carmack on the Goose Language: multiple data stacks and relative references

https://twitter.com/ID_AA_Carmack/status/2113704269274636568
8•bobbydigitales•17m ago•0 comments

Symbolic Learning in Python and Julia

https://github.com/astroautomata/PySR
23•alex_hirner•3d ago•2 comments

Node2Shell evolves to HTTP2Shell, blast radius affects many HTTP libs and apps

https://www.aikido.dev/blog/python-packages-vulnerable-node2shell-brotli-cve-2026-111497
225•theanonymousone•11h ago•105 comments

OBS Studio 33

https://github.com/obsproject/obs-studio/releases/tag/33.0.0
402•pentagrama•14h ago•140 comments

PHP Foundation 'under-funded' with one full-time staff member, director says

https://www.reuters.com/technology/php-foundation-under-funded-with-one-full-time-staff-member-di...
17•firesteelrain•20m ago•2 comments

Kimi K3.1 Pro and K3.1 Pro Highspeed

https://www.kimi.ai/blog/kimi-k3-1-pro
1052•Jowsey•1d ago•640 comments

TornadoVM 7 Enables GPU-Native Workloads from Java Applications

https://www.infoq.com/news/2026/10/tornadovm-7-gpu/
71•pjmlp•2d ago•13 comments

Physicists trap a single antimatter particle for a month

https://www.scientificamerican.com/article/physicists-trap-a-single-antimatter-particle-for-a-month/
240•mooreds•2d ago•71 comments

Danish Government silently drops plan to dump MS Office

https://www.computerworld.dk/art/297226/digitaliseringsministeriet-har-i-al-stilhed-droppet-stort...
38•lowkeyokay•53m ago•7 comments

GPU-unlock: FP/BF16 instruction issue rate on Nvidia 3000's cards

https://github.com/Zagitta/gpu-unlock
117•fragebogen•9h ago•48 comments

Today, we hacked what we'd set out to hack: the iPhone

https://blog.calif.io/p/iphone
1058•pavel_lishin•1d ago•656 comments

I Don't Understand Quantum Physics (2018)

https://www.southampton.ac.uk/~doug/quantum_physics/index.html
233•rramadass•9h ago•167 comments

Oai-math-revised: a community hub for revising OpenAI's math write-ups

https://terrytao.wordpress.com/2026/10/24/oai-math-revised-a-community-hub-for-revising-openais-m...
14•tokepi•3h ago•11 comments

Cecilia Berdichevsky, Clementina expert (1961)

https://en.wikipedia.org/wiki/Cecilia_Berdichevsky
19•fedecaccia•3d ago•0 comments

Twelve years of distributed SQLite

https://philipotoole.com/twelve-years-of-distributed-sqlite/
339•otoolep•18h ago•51 comments

Local Wikipedia: Wikipedia, but only for things a half hour walk from you

https://edjefferson.com/localwiki/
1505•sohkamyung•1d ago•240 comments

Apple Music 404 Not Found

https://music.apple.com/this-url-doesnt-exist
893•frizlab•1d ago•265 comments

Zac-OS-9: The classic Platinum desktop, reborn for modern PCs

https://sourceforge.net/projects/zac-os-9/
12•felixding•2d ago•2 comments

How close can pure functional programming get to C?

https://rtfeldman.com/fp-vs-c
226•stmonty•15h ago•65 comments

Parsing EDIFACT in Python with syntax trees

https://github.com/AmadeusITGroup/Edison
18•alexprengere•2d ago•7 comments

A practical guide to AI image generation, from diffusion to agents

https://danielball.com/notes/ai_image_generation.html
222•westsmith•4d ago•69 comments

Bringing uv and ty together

https://astral.sh/blog/uv-ty-integration
263•Ravencentric•3d ago•90 comments

Tiling Noise – Procedural GPU Patterns

https://catlikecoding.com/godot/procedural-gpu-patterns/09-tiling-noise/
42•ibobev•3d ago•1 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.