frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Flock Wants a Closely Surveilled World with No Exit

https://www.newyorker.com/culture/infinite-scroll/flock-wants-a-closely-surveilled-world-with-no-...
157•pseudolus•1h ago•127 comments

Desert Ant Labs: local, fast models that run on device

https://desertant.com/blog/introducing-desert-ant-labs/
41•willwhitedc•50m ago•4 comments

I advertise malicious software on Google Ads

https://xlii.space/eng/malicious-software-on-google-ads/
35•xlii•46m ago•15 comments

Lotus Notes and the dangers of starting from scratch

https://buttondown.com/blog/lotus-notes-email
60•maguay•2h ago•28 comments

Muse – Meta’s personal AI agent

https://ai.meta.com/muse/
548•yks•17h ago•599 comments

How An AI math breakthrough ignited a controversy

https://www.science.org/content/article/how-ai-math-breakthrough-ignited-controversy
115•pseudolus•2h ago•110 comments

Roame (YC S23) Is Hiring Viral Content Editor

https://www.ycombinator.com/companies/roame/jobs/KuVVqSh-content-systems-builder-editor
1•zman0225•28m ago

DeepSeek launching v4.1 flash cheaper and more capable than v4 pro

52•nickweb•1h ago•8 comments

Navier-Stokes – Tristan Buckmaster [pdf]

https://cims.nyu.edu/~tristanb/statement.pdf
1777•procedurecall•1d ago•741 comments

Coyote v. Acme (1990)

https://www.newyorker.com/magazine/1990/02/26/coyote-v-acme
40•ChrisArchitect•2d ago•12 comments

Tension wood: A 'muscle' that can both bend and straighten plants

https://phys.org/news/2026-09-trees-muscle-posture-newly-role.html
131•mdp2021•6d ago•34 comments

Building a Wall Lamp from Scratch

https://mbugert.de/posts/2026-09-09-bedroom-lamp-build/
15•jcklie•2h ago•2 comments

How to build a printer

https://nishantjosh.dev/blogs/how-to-build-a-fking-printer/
375•cat-whisperer•15h ago•82 comments

Open-source 3D anatomy explorer: 2,234 selectable BodyParts3D meshes

https://github.com/ashemag/human-atlas
10•metrofun•1d ago•1 comments

AlphaGenome Atlas: a high-resolution map of human DNA

https://blog.google/innovation-and-ai/models-and-research/google-deepmind/alphagenome-atlas/
572•utiiiD•21h ago•124 comments

Researchers Spot Fake Ancient Pottery Using the Earth's Magnetic Field

https://www.smithsonianmag.com/smart-news/researchers-determine-how-to-spot-fake-ancient-pottery-...
54•cisc•3d ago•25 comments

How GPT‑5.6 Sol helps run quantum computing experiments

https://openai.com/index/codex-quantum-computing-experiments/
89•theanonymousone•5h ago•74 comments

A Biography of Lee Holloway, the Architect of Cloudflare's Technology (Part 1)

https://note.com/masakazu_urabe/n/n7815f5b64fab?hl=en
70•porridgeraisin•7h ago•16 comments

Maak.el: Lisp machine command runner in Emacs, infinitely extensible and Scheme

https://codeberg.org/jjba23/maak.el
20•jjba23•1d ago•4 comments

Mercury 2.5

https://www.inceptionlabs.ai/blog/introducing-mercury-2-5
216•Topfi•16h ago•37 comments

Large language models develop novel social biases through adaptive exploration

https://openreview.net/challenge?redirect=%2Fforum%3Fid%3Dpc7fqaOcAH
180•paimapi•14h ago•93 comments

On Really Trying (2009)

https://gwern.net/on-really-trying
72•whoami_nr•5h ago•43 comments

DaVinci Resolve 21.1

https://www.blackmagicdesign.com/media/release/20260908-03
415•tosh•22h ago•187 comments

I-have-ADHD: A skill to stop coding agents from burying the answer

https://github.com/ayghri/i-have-adhd
474•domhudson•22h ago•327 comments

“Tweet” and the bird logo apparently enter the public domain

https://blog.ericgoldman.org/archives/2026/09/tweet-and-the-bird-logo-apparently-enter-the-public...
130•progval•6h ago•77 comments

Benchmarking Qwen3.8 27B quantizations: 4-bit holds up, 1-bit collapses

https://quesma.com/blog/qwen38-27b-quantizations-benchmarked/
264•stared•21h ago•127 comments

On the Navier–Stokes Millennium Prize Problem

https://openai.com/index/navier-stokes-solution/
1282•tedsanders•19h ago•1031 comments

Tao: Open math problems being non-renewably mined by AI

https://mathstodon.xyz/@tao/117237320796901560
393•_alternator_•15h ago•348 comments

27.5KB language-agnostic WebGPU syntax highlighter

https://gpu-lexer.vercel.app/
96•bpierre•11h ago•31 comments

An Accidental Blackboard

https://martinfowler.com/articles/exploring-gen-ai/an-accidental-blackboard.html
71•saikatsg•3d ago•34 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.