frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

The Birth and Death of JavaScript (2014)

https://www.destroyallsoftware.com/talks/the-birth-and-death-of-javascript
81•subset•1h ago•40 comments

Firewood Splitting Simulator

https://screen.toys/firewood/
144•memalign•4d ago•45 comments

FarOutCompany

https://faroutcompany.com/
11•bookofjoe•28m ago•2 comments

Lisp's Influence on Ruby

https://blog.tacoda.dev/lisps-influence-on-ruby-6a54f1a7740e
83•tacoda•2d ago•0 comments

How did Atari apply side art to Arcade Cabinets?

https://arcadeblogger.com/2026/06/14/how-did-atari-apply-side-art-to-arcade-cabinets/
18•msephton•1h ago•1 comments

Caddy compatibility for zeroserve: 3x throughput and 70% lower latency

https://su3.io/posts/zeroserve-caddy-compat
11•losfair•54m ago•1 comments

Free SQL→ER diagram tool, runs in the browser, nothing uploaded

https://sqltoerdiagram.com/
279•robhati•10h ago•54 comments

Honda Civics and the Evil Valet

https://juniperspring.org/posts/honda-evil-valet/
344•librick•13h ago•76 comments

How to Earn a Billion Dollars

https://paulgraham.com/earn.html
113•kingstoned•2h ago•263 comments

GLM 5.2 Is Out

https://twitter.com/jietang/status/2065784751345287314
694•aloknnikhil•22h ago•406 comments

SpaceX, Adding It Up – The $235B Cash Gap

https://capefearadvisors.substack.com/p/spacex-adding-it-up-the-235-billion
17•root-parent•24m ago•1 comments

Noise infusion banned from statistical products published by Census Bureau

https://desfontain.es/blog/banning-noise.html
859•nl•1d ago•538 comments

Historic co-determination helps monasteries navigate digital change

https://phys.org/news/2026-05-historic-monasteries-digital-countries.html
57•indynz•2d ago•39 comments

Every Frame Perfect

https://tonsky.me/blog/every-frame-perfect/
792•ravenical•1d ago•260 comments

Windows 1.0 and the WinAPI, 40 Years Later

https://medium.com/@stassaf.uae/windows-1-0-and-the-winapi-40-years-later-abaf64832918
38•jhack•2d ago•26 comments

KPMG pulls report on AI usage due to apparent hallucinations

https://techcrunch.com/2026/06/13/kpmg-pulls-report-on-ai-usage-due-to-apparent-hallucinations/
13•Brajeshwar•36m ago•2 comments

Don't trust large context windows

https://garrit.xyz/posts/2026-05-06-dont-trust-large-context-windows
179•computersuck•8h ago•127 comments

New pancreatic cancer drug might open the door to much longer survival times

https://economist.com/science-and-technology/2026/06/12/treating-pancreatic-tumours-may-have-reve...
408•andsoitis•1d ago•141 comments

Pac-Man, but you're the ghost

https://garrit.xyz/posts/2026-06-13-pac-man-but-you-re-the-ghost
153•mindracer•10h ago•66 comments

FreeOberon – Open-Source, Cross-Platform, Free Pascal/Turbo Pascal-Like Language

https://github.com/kekcleader/FreeOberon
122•peter_d_sherman•3d ago•53 comments

Tribblix: The retro Illumos distribution

http://tribblix.org/
61•naturalmovement•9h ago•20 comments

Python 3.14 garbage collection rigamarole

https://theconsensus.dev/p/2026/06/06/python-3-14-garbage-collection-rigamarole.html
74•eatonphil•2d ago•50 comments

Conversations with a six-year-old on functional programming (2018)

https://byorgey.wordpress.com/2018/05/06/conversations-with-a-six-year-old-on-functional-programm...
6•downbad_•26m ago•0 comments

Codex for open source

https://openai.com/form/codex-for-oss/
254•EvgeniyZh•2d ago•110 comments

Pyodide 314.0: Python packages can now publish WebAssembly wheels to PyPI

https://blog.pyodide.org/posts/314-release/
152•agriyakhetarpal•4d ago•36 comments

Building a serial and VGA "everything console"

http://oldvcr.blogspot.com/2026/06/building-serial-and-vga-everything.html
49•classichasclass•12h ago•5 comments

Making Claude a Chemist

https://www.anthropic.com/research/making-claude-a-chemist
68•gmays•11h ago•64 comments

A low-carbon computing platform from your retired phones

https://research.google/blog/a-low-carbon-computing-platform-from-your-retired-phones/
309•vikas-sharma•1d ago•163 comments

Phoenix LiveView 1.2

https://phoenixframework.org/blog/phoenix-liveview-1-2-released
163•ksec•9h ago•44 comments

Arch Linux AUR Hit by Another Wave of Now More Sophisticated Malware Attack

https://www.phoronix.com/news/Arch-Linux-AUR-More-Malware
10•ImJamal•1h ago•2 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.