frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

The "$60 Gaming PC" – AMD BC-250 (2025)

https://devquasar.com/hardware/the-60-gaming-pc-amd-bc-250/
107•networked•2h ago•32 comments

Actively exploited sandbox RCE in all Chromium versions

https://nvd.nist.gov/vuln/detail/cve-2026-85046
645•negura•18h ago•363 comments

Discovery of a new OpenAI agent message board

https://collusion.wiki/
1885•moultano•1d ago•1436 comments

Nitter has more working instances than before the takedowns

https://codeberg.org/mv12star/shitter/wiki/Instances
425•Cider9986•16h ago•173 comments

Terpstra Keyboard

http://terpstrakeyboard.com/
53•cl3misch•5h ago•23 comments

How the Planet-Altering Disaster of "Forever Chemicals" Was Kept Secret

https://www.propublica.org/podcast/forever-chemicals-pfas-pfos-3m-secret-kris-hansen
73•stevenwoo•1h ago•10 comments

Formalizing Fermat's Last Theorem

https://www.anthropic.com/research/formalizing-fermats-last-theorem
686•jlebar•21h ago•431 comments

Git hosting that never leaves Europe

https://pushin.eu
192•sevenseacat•9h ago•101 comments

Claude's new system prompt doesn't want to reproduce song lyrics

https://simonwillison.net/2026/Sep/2/claudes-new-system-prompt/
47•Bluestein•5h ago•29 comments

Global warming will exceed 1.5-degree limit, UN says

https://www.pbs.org/newshour/science/global-warming-will-exceed-1-5-degree-limit-un-says-in-repor...
210•ijidak•3h ago•185 comments

A bizarre Commodore 64 peripheral, a mime, and some pretty bad ads

https://buttondown.com/suchbadtechads/archive/spartan-and-the-mime/
15•rfarley04•3h ago•2 comments

A Million Falcons Went Missing. Here’s How They Were Found

https://www.nationalgeographic.com/animals/article/falcons-migration-angola-falcopolis
22•bryanrasmussen•2d ago•2 comments

Netherlands pulls gold out of the US for fears of 'geopolitical unrest'

https://www.abc.net.au/news/2026-09-04/why-the-netherlands-moved-its-gold-from-us-and-canada/1071...
246•daniel_iversen•5h ago•150 comments

Meet the Ig Nobel Prize Winners

https://arstechnica.com/science/2026/09/meet-the-2026-ig-nobel-prize-winners/
40•mkl•2h ago•5 comments

Statichost.eu – European static site hosting

https://www.statichost.eu/
376•p4bl0•19h ago•174 comments

.gitignore Everything by Default

https://packagemain.tech/p/gitignore-everything-by-default
56•der_gopher•2h ago•52 comments

AI handles incidents, engineers lose touch with their systems

https://www.sylvainkalache.com/blog/ai-handles-incidents-engineers-lose-touch-with-their-systems
279•sylvainkalache•8h ago•243 comments

Can AI design circuit boards yet?

https://eebench.org/blog/can-ai-design-circuit-boards-yet/
306•iopapa•20h ago•183 comments

GPT-6 Astra on OpenRouter

https://openrouter.ai/openai/gpt-6-astra
272•Topfi•18h ago•183 comments

Portal by Spotify cut my Claude Code token usage by 90%

https://engineering.atspotify.com/2026/9/portal-by-spotify-cut-my-claude-code-token-usage-by-90
202•cebert•16h ago•111 comments

Shutting down our public encrypted DNS

https://mullvad.net/en/blog/shutting-down-our-public-encrypted-dns-servers-and-sponsoring-quad9-i...
401•mywacaday•21h ago•186 comments

Pointing at the error: compiler-style diagnostics in uutils coreutils

https://uutils.org/blog/2026-08-error-diagnostics/
43•ingve•3d ago•5 comments

Show HN: Open-Source eInk Bike Computer

https://opentrailpaper.com
344•stingrae•22h ago•111 comments

Write Software in Latin (2025) [video]

https://www.youtube.com/watch?v=fGZpaqMha0o
4•akkartik•2d ago•2 comments

Ask HN: Resources to get good at soldering?

184•tosmatos•3d ago•111 comments

There's No Limit to How Bad Code Can Get

https://zachkehs.com/blog/theres_no_limit_to_how_bad_code_can_get/
76•zkehs•1h ago•51 comments

IBM Bob

https://bob.ibm.com/
305•artpar•1d ago•313 comments

Rebuilding a 1995 GPS Time Server so I don't get Telstra'd

https://www.jeffgeerling.com/blog/2026/truetime-xl-gps-time-server-restomod/
5•Brajeshwar•46m ago•0 comments

Git Submodules as a Package Manager

https://nesbitt.io/2026/09/01/git-submodules-as-a-package-manager.html
76•ErenayDev•4d ago•20 comments

Fermat's Last Theorem in Lean 4

https://github.com/anthropics/fermats-last-theorem
136•aaraujo002•21h ago•27 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.