frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

MiMo Code Is Now Released and Open-Source

https://mimo.xiaomi.com/mimocode
116•apeters•1h ago•46 comments

Lines of Code Got a Better Publicist

https://curlewis.co.nz/posts/lines-of-code-got-a-better-publicist/
203•RyeCombinator•3h ago•136 comments

MapComplete – Contibute to OpenStreetMaps

https://mapcomplete.org/
87•GTP•1h ago•18 comments

FPS.cob: A first person shooter in COBOL

https://github.com/icitry/FPS.cob
26•MBCook•45m ago•2 comments

Nextcloud Hub 26 Spring: Built together, designed for the future

https://nextcloud.com/blog/nextcloud-hub26-spring/
61•doener•1h ago•31 comments

Pokémon Go Scans Trained the Navigation Tech for Military Drones

https://dronexl.co/2026/06/09/pokemon-go-scans-niantic-vantor-military-drone-navigation/
565•vrganj•9h ago•256 comments

Open Reproduction of DeepSeek-R1

https://github.com/huggingface/open-r1
76•yogthos•2h ago•10 comments

Workers are spending over 6 hours a week botsitting AI, fueling job frustration

https://www.businessinsider.com/botsitting-ai-hidden-human-labor-at-work-2026-6
175•ZeidJ•2h ago•130 comments

Queues Don't Fix Overload (2014)

https://ferd.ca/queues-don-t-fix-overload.html
15•locknitpicker•2d ago•4 comments

AI agent runs amok in Fedora and elsewhere

https://lwn.net/SubscriberLink/1077035/c7e7c14fbd60fae9/
521•tanelpoder•15h ago•230 comments

Why Thermodynamics Rules Future Orbital Data Centers

https://spectrum.ieee.org/orbital-data-centers-heat
30•rbanffy•2h ago•34 comments

Web Browsers on Video Game Consoles

https://vale.rocks/posts/game-console-browsers
125•robin_reala•7h ago•61 comments

Cybersecurity researchers aren't happy about the guardrails on Anthropic's Fable

https://techcrunch.com/2026/06/10/cybersecurity-researchers-arent-happy-about-the-guardrails-on-a...
551•speckx•23h ago•485 comments

πFS

https://github.com/philipl/pifs
898•helterskelter•21h ago•198 comments

Anthropic requires 30 day data retention for Fable and Mythos

https://support.claude.com/en/articles/15425996-data-retention-practices-for-mythos-class-models
568•lebovic•1d ago•287 comments

Build a Basic AI Agent from Scratch: Long Task Planning

https://medium.com/@rogi23696/build-a-basic-ai-agent-from-scratch-long-task-planning-14e803f9bd6d
100•ruxudev•2d ago•41 comments

Driving in America Is Headlight Hell

https://www.theatlantic.com/technology/2026/06/car-headlights-too-bright-adaptive-beams/687488/
44•pavel_lishin•1h ago•21 comments

Show HN: Open-source API Key server written in Go by Ory

https://github.com/ory/talos/tree/master
12•leetvibecoder•49m ago•2 comments

Supporting Exchange and beyond

https://brendan.abolivier.bzh/exchange-pt-2/
9•babolivier•2d ago•1 comments

Linux latency measurements and compositor tuning

https://farnoy.dev/posts/linux-latency
100•GalaxySnail•2d ago•30 comments

Euro-Office: First version of the open-source web office is here

https://www.heise.de/en/news/Euro-Office-First-version-of-the-open-source-web-office-is-here-1132...
45•doener•1h ago•18 comments

I'm Eric Ries, author of "The Lean Startup" and new book "Incorruptible" – AMA

752•eries•1d ago•520 comments

US-Canada border library gets new Quebec-only entrance

https://www.bbc.com/news/videos/clyrvrde160o
92•NalNezumi•2h ago•77 comments

Why AI hasn't replaced software engineers, and won't

https://www.normaltech.ai/p/why-ai-hasnt-replaced-software-engineers
192•trueduke•8h ago•239 comments

Starfish by Peter Watts (1999)

https://www.rifters.com/real/STARFISH.htm#prelude
117•zetalyrae•2d ago•47 comments

Reverse engineering the Creative Katana soundbar to control it from Linux

https://blog.nns.ee/2026/02/20/katana-v2x-re/
119•theanonymousone•4d ago•10 comments

Sequoyah’s syllabary created a written language for the Cherokee

https://www.smithsonianmag.com/innovation/man-created-written-language-cherokee-did-efficiently-e...
184•grahambargeron•17h ago•116 comments

PgDog is funded and coming to a database near you

https://pgdog.dev/blog/our-funding-announcement
522•levkk•1d ago•245 comments

How JPL keeps the 13-year-old Curiosity rover doing science

https://spectrum.ieee.org/curiosity-rover-jpl-mars-science
266•pseudolus•22h ago•83 comments

L'Affaire Siloxane

https://mceglowski.substack.com/p/laffaire-siloxane
274•idlewords•2d ago•48 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.