frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Stolen Buttons

https://anatolyzenkov.com/stolen-buttons
257•Gecko4072•5d ago•65 comments

Open-weight AI is having its Kubernetes moment

https://tobi.knaup.me/2026-07-25-open-weight-ai-is-having-its-kubernetes-moment/
127•tknaup•3h ago•83 comments

Android May Soon Restrict On-Device ADB

https://kitsumed.github.io/blog/posts/android-may-soon-restrict-on-device-adb/
723•shscs911•11h ago•323 comments

Bitchat Is Now on Radicle

https://radicle.network/nodes/rosa.radicle.network/rad%3Az2v9tRJz1oknFAqCSY5W5c76nVvm6
113•h1watt•5h ago•52 comments

GDID Windows – Cut the tracker that follows you even under VPN

https://korben.info/en/gdid-windows-cut-tracker-vpn.html
28•rfarley04•4d ago•20 comments

How My Images Are Dithered

https://dead.garden/blog/how-my-images-are-dithered.html
153•surprisetalk•3d ago•60 comments

Bringing PyTorch Monarch to AMD GPUs

https://pytorch.org/blog/bringing-pytorch-monarch-to-amd-gpus-single-controller-distributed-train...
24•gmays•2h ago•5 comments

Tile's Security Is So Bad It's a Feature for Stalkers

https://blog.adafruit.com/2026/03/05/tiles-security-is-so-bad-its-a-feature-for-stalkers/
4•sambellll•11m ago•0 comments

Rauno's Field Notes #2

https://rauno.me/notes/2
14•acmnrs•1h ago•1 comments

Spatial languages: Writing code in 2D

https://shukla.io/blog/2026-07/cccx.html
77•BinRoo•3d ago•25 comments

The Fedora 45 Sausage Factory

https://supakeen.com/weblog/the-fedora-45-sausage-factory/
97•6581•7h ago•29 comments

Hannah Fry Wins the Leelavati Prize in 2026 for Mathematics Outreach

https://www.maths.cam.ac.uk/features/professor-hannah-fry-wins-leelavati-prize
523•agnishom•16h ago•87 comments

Zero roadkill as Amazon canopy bridges secure 15,000 crossings

https://news.mongabay.com/2026/07/zero-roadkill-as-amazon-canopy-bridges-secure-15000-crossings/
130•hn_acker•3d ago•28 comments

The Dark Night of Mathematics

https://kirwinhampshire.substack.com/p/the-dark-night-of-mathematics
58•rmdmphilosopher•2h ago•43 comments

Building a Tiny 3D Renderer for a Tiny Handheld

https://saffroncr.itch.io/katavatis/devlog/1534514/building-a-tiny-3d-renderer-for-a-tiny-handheld
188•g0xA52A2A•3d ago•14 comments

Wind turbine is being used to produce zero-carbon "green ammonia" fertilizer

https://energiesmedia.com/wind-turbine-stopped-electricity-wind-water-air/
75•speckx•2h ago•61 comments

Engineering management after the cost of code collapsed

https://karimjedda.com/engineering-management-after-cost-of-code-collapse/
52•kiyanwang•3h ago•73 comments

Scanwheel is a drum style mechanical television you can build yourself

https://github.com/AncientJames/Scanwheel/
27•tobr•4h ago•5 comments

Kyber (YC W23) Is Hiring a Head of Engineering

https://www.ycombinator.com/companies/kyber/jobs/FGmI8mx-head-of-engineering
1•asontha•6h ago

The Silurian Hypothesis (2020)

https://www.theparisreview.org/blog/2020/01/23/the-silurian-hypothesis/
33•andsoitis•4h ago•69 comments

NYC Apartment Aquaponics

https://erinmurphy.dev/projects/project-2/
163•mm1119•5d ago•67 comments

Charles Ross spent 50 yrs building Star Axis naked-eye observatory in New Mexico

https://www.nytimes.com/2026/07/22/arts/design/charles-ross-star-axis-land-art.html
87•ChrisArchitect•2d ago•18 comments

ARC-AGI Leaderboard

https://arcprize.org/leaderboard
165•rzk•11h ago•127 comments

MouthPad: A Tongue-Controlled Touchpad

https://www.augmental.tech/
119•ZaninAndrea•10h ago•26 comments

Task-centered iproute2 user guide

https://baturin.org/docs/iproute2/
18•greengreengrass•3h ago•0 comments

Teardown: The BMW / Harman IDC23H Infotainment Unit (B423)

https://www.hakstuff.net/blog/teardown-the-bmw-idc23h-infotainment-unit
12•JojoFatsani•2d ago•6 comments

Brazilian farmers tokenized dairy cows to get loans, bypassing bank limits

https://www.coindesk.com/markets/2026/07/24/brazilian-farmers-tokenized-dairy-cows-to-get-loans-b...
40•paulpauper•2h ago•26 comments

PyPI Blog: Releases now reject new files after 14 days

https://blog.pypi.org/posts/2026-07-22-releases-now-reject-new-files-after-14-days/
74•miketheman•3d ago•38 comments

My web version of Mars MIPS, now have builtin C compiler

https://webmars.nfiles.top/
14•nenepbl•4h ago•4 comments

GC and Exceptions in Wasmtime

https://bytecodealliance.org/articles/wasmtime-gc
143•phickey•5d ago•25 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.