frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Hacking OpenAI

https://www.hacktron.ai/blog/hacking-openai
251•Handy-Man•4h ago•86 comments

Jemalloc 5.4.0

https://github.com/jemalloc/jemalloc/releases/tag/5.4.0
41•gkfasdfasdf•2h ago•7 comments

The scourge of x86 emulation

https://fex-emu.com/Scourge-of-emulation/
52•dagmx•2h ago•1 comments

Astra for Law

https://openai.com/index/astra-for-law/
444•vertigoruntime•10h ago•465 comments

Bonsai 2 27B: Near-Lossless Compression in a 9x Smaller Footprint

https://prismml.com/news/bonsai-2-27b
375•JonSchneider•9h ago•115 comments

Bend – A language that blocks AI mistakes via proof, on CPU and GPU

https://bend-lang.com/
411•nicolas-siplis•10h ago•198 comments

Pre-Greek: The lost language hidden within Ancient Greek

https://linguisticdiscovery.com/posts/pre-greek/
50•axiologist•3h ago•16 comments

Hister: A private search engine for the pages you visit and the files you keep

https://github.com/asciimoo/hister
562•bookofjoe•14h ago•150 comments

Qwen 3.8 Omni Flash

https://qwen.ai/blog?id=qwen3.8-omni-flash
154•jjcm•7h ago•49 comments

Wax motor

https://en.wikipedia.org/wiki/Wax_motor
340•mhb•1d ago•62 comments

Fujitsu launches made-in-Japan next-generation CPU FUJITSU-MONAKA

https://global.fujitsu/en-global/pr/news/2026/09/14-02
568•my123•2d ago•214 comments

Waymo in Singapore

https://waymo.com/waymo-in-singapore/
92•ramanan•3h ago•75 comments

Shapelearn Qwen 3.8 27B (13.1 GB VRAM)

https://byteshape.com/blogs/Qwen3.8-27B/
41•syntaxing•5h ago•4 comments

Apple detectives solved mystery of ancient tree and rewrote the history of fruit

https://www.scientificamerican.com/article/how-apple-detectives-solved-the-mystery-of-an-ancient-...
32•nkurz•1d ago•3 comments

Telstra outage: The night a network decided the year was 2006

https://www.netnod.se/blog/telstra-outage-night-network-decided-year-was-2006
44•TMWNN•5h ago•17 comments

How to Write with an LLM

https://sockpuppet.org/blog/2026/09/17/how-to-write-with-an-llm/
112•joeriddles•9h ago•73 comments

Flet 1.0 – Build cross-platform apps in Python

https://flet.dev/
98•absqueued•10h ago•46 comments

Fixing an NZXT Signal 4K30 part 2: the green/pink video bug

https://www.downtowndougbrown.com/2026/09/fixing-an-nzxt-signal-4k30-part-2-the-green-pink-video-...
26•zdw•4d ago•8 comments

Ask A Monk – A digital wilderness for thoughts with no immediate answer

https://askamonk.online
28•13613288957•5h ago•17 comments

Diplodocus, Long Thought Exclusively American, Turns Up in Spain

https://www.sci.news/paleontology/spanish-diplodocus-15064.html
57•embedding-shape•2d ago•33 comments

The most important product decision is what you don't build

https://liamnugent.me/posts/what-you-dont-build/
88•ChrisArchitect•10h ago•27 comments

CrowdSec Source Code Leak

https://www.crowdsec.net/blog/crowdsec-statement-source-code-exposure
146•eccgecko•15h ago•43 comments

How do we prevent mathemathics from devolving into the Medieval Era of secrecy?

https://mathoverflow.net/questions/515260/how-do-we-prevent-mathematics-from-devolving-into-the-m...
105•jjgreen•2d ago•86 comments

Khipu (Quipu) Field Guide

https://www.khipufieldguide.com/
10•SanjayMehta•2d ago•1 comments

How Uber Protects Against Retry Storms

https://www.uber.com/us/en/blog/protecting-against-retry-storms/
85•iscmt•9h ago•33 comments

Why I didn’t sign the Fields medallists’ letter

https://gowers.wordpress.com/2026/09/17/why-i-didnt-sign-the-fields-medallists-letter/
239•simianwords•22h ago•340 comments

Code Scans

https://devin.ai/blog/introducing-code-scans
15•geoffbp•4h ago•4 comments

Show HN: Snapdrop: Instantly share files between devices. No setup, no signup

https://snapdrop.me
64•Capira•10h ago•31 comments

Minimal Phone 2

https://minimalcompany.com/
33•nashashmi•5h ago•16 comments

Infinite-Parameter LLMs: Generating and Adapting Weights from Live Data

https://arxiv.org/abs/2609.18842
135•Betelbuddy•14h ago•38 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.