frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Discovery of a new OpenAI agent message board

https://collusion.wiki/
232•moultano•1h ago•136 comments

Solving the Jane Street Reverse Engineering Challenge

https://jestoph.com/2026/09/04/jane-street-challenge.html
155•anitil•3h ago•46 comments

GPT-6 Astra

https://openai.com/index/gpt-6-astra/
1934•kibae•18h ago•1738 comments

O&O ShutUp10 – The antispy tool for Windows 10 and 11

https://www.oo-software.com/en/shutup10
43•embedding-shape•2h ago•18 comments

IBM Bob

https://bob.ibm.com/
17•artpar•40m ago•11 comments

.name Termination

https://neil.fraser.name/news/2026/09/03/
1983•pavel_lishin•22h ago•487 comments

Ok, but Does It Scale?

https://spacetimedb.com/blog/how-does-spacetime-scale
15•theanonymousone•49m ago•0 comments

Restoring 5 GHz Wi-Fi on an LG C5 by changing its webOS region

https://github.com/hawshemi/lg-c5-webos25-region-change
12•hawshemi•41m ago•5 comments

SubImage (YC W25) Is Hiring a Founding Engineer in SF

https://www.ycombinator.com/companies/subimage/jobs/NCTFgKK-founding-engineer
1•alexchantavy•1h ago

Elevator of the Year Winner Modernization of the Metropolis Trust Building

https://www.starelevator.com/projects/star-elevator-modernization-of-the-metropolis-trust-building
43•palashawas•3d ago•14 comments

Qwen 3.8 27B available on Cerebras at 1500 tokens/s

https://inference-docs.cerebras.ai/models/overview
608•altertable•18h ago•202 comments

Why is Arrays.fill 265 times slower on G1GC?

https://krzysztofslusarski.github.io/2026/08/19/g1barrier.html
9•ejboy•3d ago•1 comments

Nearly impossible? How Fairphone built the ethical, repairable Fairphone Gen 6+

https://arstechnica.com/gadgets/2026/09/nearly-impossible-how-fairphone-built-the-ethical-repaira...
17•CrypticShift•47m ago•11 comments

Authorization terminology is a mess: Let's fix it

https://idpro.org/authorization-terminology-is-a-mess-lets-fix-it/
81•andychiare•2d ago•53 comments

Hackers Had a Live Feed of Every ID Verification Company Scanned for over a Year

http://www.techdirt.com/2026/09/03/hackers-had-a-live-feed-of-every-id-this-verification-company-...
311•beardyw•6h ago•119 comments

The largest electric aircraft just flew [video]

https://www.youtube.com/watch?v=nM86DBOqgPM
385•feb•2d ago•274 comments

Artificial beaver dams saw juvenile coho salmon survival rates go from 8% to 60%

https://www.discoverwildlife.com/animal-facts/artificial-beaver-dams-california
300•speckx•21h ago•94 comments

How an MIT research project became the Julia programming language

https://news.mit.edu/2026/how-mit-research-project-became-global-programming-language-0831
144•theanonymousone•4d ago•70 comments

Go grandmaster Shin defeats AI KataGo with a two-stone handicap

https://www.kedglobal.com/artificial-intelligence/newsView/ked202607210007
378•gmays•1d ago•141 comments

Porting my 1993 Amiga game to Godot, with an LLM reading the 68000 assembly

https://babyloniantwins.com/blog/porting-a-1993-amiga-game-to-godot/
322•rabahs•23h ago•106 comments

Carbon-aware electricity pricing, measured daily on 38 grids

https://carbonawarepricing.com/
69•High-Five•5h ago•50 comments

Project Xanadu: Even More Hindsight (2025)

https://gwern.net/xanadu
98•andsoitis•11h ago•27 comments

1960s theory that Stonehenge was a prehistoric computer

https://www.bbc.com/culture/article/20260828-the-startling-1960s-theory-that-stonehenge-was-a-pre...
51•dabinat•4d ago•56 comments

Which tools do Claude, Codex and Cursor choose? We measured 17k runs to find out

https://armature.tech/blog/which-tools-coding-agents-install
253•screm•16h ago•117 comments

K2 Horizon: A connected fleet of six open models

https://ifm.ai/blog/k2/
312•karimf•21h ago•115 comments

Ask HN: Who is using MCP in production?

109•sukit•1d ago•130 comments

GPS glitched across the US by as much as 33 feet

https://www.sciencealert.com/gps-glitched-across-the-us-by-as-much-as-33-feet-scientists-have-nev...
198•thread_id•1d ago•118 comments

Move in C++ without a std:move

https://andreasfertig.com/blog/2026/09/move-in-cpp-without-a-stdmove/
57•dalvrosa•3d ago•64 comments

Oscar Winner Brings Monsters to Life with His Simulation Software

https://spectrum.ieee.org/oscar-winner-jernej-barbic
18•jruohonen•3d ago•1 comments

Xanadu was waiting for agents

https://zed.dev/blog/agentic-xanadu
137•nsm•2d ago•57 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.