frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Europe's next-generation weather satellite sends back first images

https://www.esa.int/Applications/Observing_the_Earth/Meteorological_missions/meteosat_third_gener...
196•saubeidl•3h ago•31 comments

Render Mermaid diagrams as SVGs or ASCII art

https://github.com/lukilabs/beautiful-mermaid
247•mellosouls•8h ago•39 comments

We can't send mail farther than 500 miles (2002)

https://web.mit.edu/jemorris/humor/500-miles
374•giancarlostoro•6h ago•43 comments

Apple to soon take up to 30% cut from all Patreon creators in iOS app

https://www.macrumors.com/2026/01/28/patreon-apple-tax/
397•pier25•13h ago•326 comments

Decompiling Xbox games using PDB debug info

https://i686.me/blog/csplit/
38•orange_redditor•2d ago•0 comments

The Chemistry of Tea [pdf]

https://www.researchgate.net/profile/Matthew-Harbowy/publication/216792045_Tea_Chemistry/links/09...
26•aabiji•5d ago•1 comments

Maine’s ‘Lobster Lady’ who fished for nearly a century dies aged 105

https://www.theguardian.com/us-news/2026/jan/28/maine-lobster-lady-dies-aged-105
141•NaOH•8h ago•17 comments

Mecha Comet – Open Modular Linux Handheld Computer

https://mecha.so/comet
140•Realman78•3d ago•43 comments

Xmake: A cross-platform build utility based on Lua

https://xmake.io/
49•phmx•3d ago•18 comments

Airfoil (2024)

https://ciechanow.ski/airfoil/
464•brk•19h ago•51 comments

Trinity large: An open 400B sparse MoE model

https://www.arcee.ai/blog/trinity-large
189•linolevan•1d ago•58 comments

Tesla ending Models S and X production

https://www.cnbc.com/2026/01/28/tesla-ending-model-s-x-production.html
313•keyboardJones•11h ago•558 comments

Show HN: A MitM proxy to see what your LLM tools are sending

https://github.com/jmuncor/sherlock
173•jmuncor•15h ago•86 comments

Mousefood – Build embedded terminal UIs for microcontrollers

https://github.com/ratatui/mousefood
208•orhunp_•17h ago•44 comments

Android's desktop interface leaks

https://9to5google.com/2026/01/27/android-desktop-leak/
242•thunderbong•1d ago•319 comments

Did a celebrated researcher obscure a baby's poisoning?

https://www.newyorker.com/magazine/2026/02/02/did-a-celebrated-researcher-obscure-a-fatal-poisoning
154•littlexsparkee•1d ago•53 comments

How London became the rest of the world’s startup capital

https://www.economist.com/britain/2026/01/26/how-london-became-the-rest-of-the-worlds-startup-cap...
115•ellieh•1d ago•124 comments

An Illustrated Guide to Hippo Castration (2014)

https://www.science.org/content/article/scienceshot-illustrated-guide-hippo-castration
65•joebig•4d ago•24 comments

Satellites encased in wood are in the works

https://www.economist.com/science-and-technology/2026/01/21/satellites-encased-in-wood-are-in-the...
59•andsoitis•3d ago•35 comments

Questom (YC F25) is hiring an engineer

https://www.ycombinator.com/companies/questom/jobs/UBebsyO-founding-engineer
1•ritanshu•6h ago

Why do RSS readers look like email clients?

https://www.terrygodier.com/phantom-obligation
45•zdw•4h ago•21 comments

In a genre where spoilers are devastating, how do we talk about puzzle games?

https://thinkygames.com/features/in-a-genre-where-information-is-sacred-and-spoilers-are-devastat...
68•tobr•5d ago•56 comments

The Only Moat Left Is Knowing Things

https://growtika.com/blog/authenticity-edge
28•Growtika•2h ago•13 comments

LM Studio 0.4

https://lmstudio.ai/blog/0.4.0
152•jiqiren•16h ago•80 comments

Oban, the job processing framework from Elixir, has come to Python

https://www.dimamik.com/posts/oban_py/
231•dimamik•17h ago•90 comments

OpenAI's Unit Economics

https://www.exponentialview.co/p/inside-openais-unit-economics-epoch-exponentialview
5•swolpers•2h ago•0 comments

Computer History Museum Launches Digital Portal to Its Collection

https://computerhistory.org/press-releases/computer-history-museum-launches-digital-portal-to-its...
155•ChrisArchitect•16h ago•26 comments

Bf-Tree: modern read-write-optimized concurrent larger-than-memory range index

https://github.com/microsoft/bf-tree
86•SchwKatze•12h ago•16 comments

Somebody used spoofed ADSB signals to raster the meme of JD Vance

https://alecmuffett.com/article/143548
492•wubin•12h ago•125 comments

Show HN: Externalized Properties, a modern Java configuration library

https://github.com/joel-jeremy/externalized-properties
4•jeyjeyemem•2d ago•1 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•8mo ago

Comments

tonyarkles•8mo 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•8mo ago
You can convert edge coloring problems into vertex coloring problems and vice versa through a simple O(n) procedure.
meindnoch•8mo 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•8mo ago
Indeed. Thanks, I stand corrected.
tonyarkles•8mo 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•8mo 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•8mo 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•8mo ago
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•8mo 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•8mo 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•8mo 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.
phkahler•8mo ago
Is this going to lead to faster compile times? Faster register allocation...
john-h-k•8mo ago
Very few compilers actually use vertex coloring for register allocation
isaacimagine•8mo 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•8mo ago
and this post isn't even about vertex coloring
DannyBee•8mo 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.