frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Meta’s new commercial terms will allow the scraping of news sites: experts

https://www.niemanlab.org/2026/10/metas-new-commercial-terms-will-allow-the-scraping-of-news-site...
287•0in•10h ago•103 comments

Muse Spark Open

https://research.meta.ai/blog/muse-spark-open
810•bigwheels•15h ago•402 comments

Woman who rescued injured crow keeps getting 'thank-you gifts' from birds [video]

https://www.youtube.com/watch?v=sjNpfz4UzqU
286•johnnyApplePRNG•3d ago•90 comments

The insider trading you're allowed to do

https://coached.com/essays/the-insider-trading-youre-allowed-to-do/
22•rohanm93•2h ago•10 comments

RPKI now protects 70% of internet routes

https://ipinfo.io/blog/rpki-protects-70-internet-routes
156•emot•8h ago•48 comments

The Folders Programming Language

https://danieltemkin.com/esolangs/folders
52•gurst•4h ago•8 comments

New York City's iconic horse-drawn carriages expected to take their last trot

https://www.cnn.com/2026/10/13/us/nyc-horse-carriage-ban
37•1659447091•2d ago•24 comments

Neural networks are clean

https://already-clean.goodfire.com/
681•themgt•17h ago•253 comments

Two-Stack Sliding-Window Aggregation

https://orlp.net/blog/two-stack-sliding-window-aggregation/
9•surprisetalk•2d ago•0 comments

What I self-host

https://viceconsole.fyi/blog/2026/10/10/what-i-self-host/
479•BrunoBernardino•13h ago•297 comments

New Withings Users Must Pay $99/Year for Apple Health Syncing

https://support.withings.com/hc/en-us/community/posts/51887047154577-Unacceptable-Apple-Health-Sy...
288•johnbehnke•13h ago•184 comments

Wayland desktop for Linux with skeuomorphic design

https://github.com/fyzugx/DEsk
609•FinalDestiny•20h ago•237 comments

Apple routed a graphite pipe through the iPhone Duo's hinge to dissipate heat

https://www.pcmag.com/news/apple-routed-a-graphite-pipe-through-the-iphone-duos-hinge
135•giuliomagnifico•3d ago•97 comments

Jev meets the Trolley Problem

https://zachlandes.com/trolley-problem/
460•zlandes86•17h ago•197 comments

BIPM decides to stop adding leap seconds to UTC

https://www.bipm.org/en/cgpm-2026/resolution-5
177•gliffie•17h ago•84 comments

Any window from your Mac, on your iPhone and iPad

https://github.com/Saffsanity/sill
144•chanana•7h ago•33 comments

'500-hour' Order of the Sinking Star is as complex and exhausting as it sounds

https://www.polygon.com/order-of-the-sinking-star-impressions/
141•cvoss•2d ago•91 comments

Someone on Torrent Sites Kept Fucking with My Sonarr

https://thereallo.dev/blog/someone-on-torrent-sites-kept-fucking-with-my-sonarr-setup
343•speckx•14h ago•153 comments

Celebrating 70 Years of Fortran

https://fortran-lang.org/news/2026/09-15-Fortran-birthday/
274•rbanffy•18h ago•112 comments

Last rites for Gentoo's Chromium package

https://lwn.net/Articles/1097760/
55•signa11•4h ago•46 comments

Krea 3 – An image model built for editing at scale

https://www.krea.ai/krea-3
308•dvrp•17h ago•99 comments

The Economic Complexity of the Western Roman Empire

https://www.michelecoscia.com/?p=2613
8•mikk14•2d ago•1 comments

Comparing Chromium Development at Google and Igalia

https://lwn.net/Articles/1094721/
48•signa11•7h ago•15 comments

Thank You, Deno

https://www.vlt.io/blog/competition-keeps-javascript-moving
77•jcbhmr•8h ago•12 comments

Why I Wrote PGP (1991, revised 1999)

https://philzimmermann.com/EN/essays/WhyIWrotePGP.html
158•GaryBluto•2d ago•54 comments

Major ICQ security hole (1998)

https://opennet.ru/base/maillist/169.txt.html
89•sysoleg•2d ago•48 comments

Libreboot 26.10 "Ominous Olive" released with UEFI, Chromebook support

https://libreboot.org/news/libreboot2610.html
289•iamnothere•20h ago•174 comments

Delta’s Biscoff cookies were supposed to be temporary

https://www.seriouseats.com/biscoff-history-12168161
221•mhb•2d ago•172 comments

Using AI to reverse engineer hardware

https://blogs.gnome.org/uraeus/2026/10/15/aiandreverseengineerhardware/
189•ErenayDev•19h ago•174 comments

BeBox is a Haiku application that emulates Be Inc.'s BeBox

https://github.com/johnrash/bebox
59•rguiscard•10h ago•15 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.