frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Software may be getting worse, but it used to be horrible

https://www.bitlog.com/2026/10/27/software-may-be-getting-worse-but-it-used-to-be-horrible/
64•jakevoytko•55m ago•31 comments

Python's experimental JIT to be removed

https://lwn.net/SubscriberLink/1102102/0c00e4d550f25f8c/
45•f311a•1h ago•5 comments

Roblox downloaded 145GB models from us (including adult content) without asking

https://open3dlab.com/news/roblox-downloaded-145-gb-of-models-from-our-sites/
156•choult•1h ago•110 comments

Wikipedia's Cleanup of AI-Generated Content

https://spectrum.ieee.org/wikipedia-wikiproject-ai-writing-cleanup
44•rbanffy•1h ago•20 comments

Three new discoveries in mathematics, computer science, and physics

https://openai.com/index/building-scientific-understanding-with-academic-communities/
971•jonluca•14h ago•514 comments

The Mythical Man-Month in the Age of AI

https://j11g.com/the-mythical-man-month-in-the-age-of-ai
231•ilreb•6h ago•157 comments

Gforth 1.0

https://gforth.org/manual/1.0/NEWS.html
32•joshcsimmons•2h ago•2 comments

The Exponential Time Hypothesis Is False [pdf]

https://github.com/openai/math/blob/main/preprints/The-Exponential-Time-Hypothesis-is-False-Octob...
669•vok•14h ago•250 comments

AI promised less work. I've never worked more

https://oioannou.com/blog/ai-promised-less-work/
6•oorestisime•1h ago•1 comments

Sebastian Raschka's from-scratch video course on building reasoning models

https://magazine.sebastianraschka.com/p/building-reasoning-models
741•sgiannopoulos•21h ago•102 comments

I will no longer upload to NEW

https://lists.debian.org/debian-devel/2026/10/msg00263.html
128•edward•2h ago•56 comments

Oldest GUI application that still runs on Windows 11

https://blog.enlyth.com/posts/oldest-windows-gui-app-win-11/
462•enlyth•18h ago•275 comments

I still teach OpenGL ES 3.0

https://eliasfarhan.ch/graphics/cpp/2026/01/27/why-i-teach-opengles.html
84•majorchord•10h ago•55 comments

Solar power is becoming bigger than nuclear

https://www.bbc.com/future/article/20261023-how-solar-became-bigger-than-nuclear
388•geox•20h ago•561 comments

Writing about pratt parsing so I remember it

https://www.unix.dog/~yosh/blog/2026-10-25_pratt-parsing.html
50•dverlaeckt80•6h ago•6 comments

Type Server Protocol

https://github.com/microsoft/pylance-release/blob/main/docs/tsp/type-server-protocol.md
249•adamnemecek•18h ago•169 comments

CSS-Tricks has a new owner

https://css-tricks.com/css-tricks-has-a-new-owner/
500•edent•20h ago•107 comments

Cross-request KV cache exposure in the GLM-5.3 Workers AI model (155 responses)

https://blog.cloudflare.com/kv-cache-exposure-remediation/
146•wondersky•13h ago•47 comments

A Printer Printing onto Paper

https://twitter.com/macrofying/status/2112904628509528219
149•MrBuddyCasino•4d ago•33 comments

16-bit Windows (Windows 1.x, 2.x, 3.0, 3.1, etc.) on 64-bit Windows

https://github.com/otya128/winevdm
102•doener•11h ago•27 comments

How to grow a cacao tree at home (2024)

https://www.cocoterra.com/guide-on-how-to-grow-chocolate-at-home/
94•felipevb•1d ago•31 comments

New iPad mini

https://www.apple.com/newsroom/2026/10/apple-gives-ipad-mini-its-biggest-update-ever/
225•soheilpro•23h ago•541 comments

Txoko: Basques' traditional feast a gastronomic peek into a culture (2024)

https://johnhendersontravel.com/txoko/
35•jxub•3d ago•11 comments

Websites Should Be Printable

https://brennenputh.me/blog/printable-websites/
357•bagatelle•1d ago•204 comments

A Man from the Future: Why Johnny Can't Stop Abstracting

http://muratbuffalo.blogspot.com/2026/10/the-man-from-future-why-johnny-cant.html
186•aray07•18h ago•85 comments

Blaise Pascal invented fixed route public transport (2024)

https://humantransit.org/2024/12/one-of-the-greatest-inventions-in-the-history-of-human-transport...
296•skadamat•4d ago•151 comments

Anthropic S-1

https://www.sec.gov/Archives/edgar/data/2130357/000162828026067168/anthropicpbc-sx1.htm
1640•SiNTEx•23h ago•1562 comments

Nietzschian Debugger

https://github.com/DilawarShafiq/nietzschian-debugger
194•dilawargopang•19h ago•57 comments

APC says let there be light, with standards to speed up photonics manufacturing

https://www.nextplatform.com/connect/2026/10/23/apc-says-let-there-be-light-with-raft-of-standard...
40•rbanffy•1d ago•8 comments

SIMD-accelerated computer vision on a $2 microcontroller

https://shraiwi.com/blog/simd-fast-esp32s3/
217•zdw•1d ago•61 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.