frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Amazon saves millions by replacing Sonnet 4.6 with Strands Decider

https://strandsagents.com/blog/amazon-saves-millions-replacing-sonnet-with-strands-decider/
190•aloukissas•2h ago•62 comments

Claude Fable 5.2 and Mythos 5.2

https://www.anthropic.com/claude-fable-and-mythos-5-2
531•lairv•14h ago•763 comments

USPS now offers official ZIP Code boundary polygons

https://postalpro.usps.com/zcb
609•munro•12h ago•303 comments

Your TV can see through walls

https://maurycyz.com/projects/fading/
76•Curiositry•3h ago•20 comments

Locating the source of a mysterious beep

https://simonwillison.net/2026/Nov/9/mysterious-beeps/
157•bigwheels•8h ago•71 comments

E-means: Outperforming k-means in one-tenth the epochs

https://e-means.github.io/
382•porridgeraisin•13h ago•36 comments

Payments Canada announces launch of Canada's Real-Time Rail (RTR) payment system

https://www.payments.ca/canada-launches-real-time-rail-bringing-247-payment-infrastructure-nation...
525•ocd•16h ago•283 comments

Foldable Flight: The Best Paper Airplanes

https://www.foldableflight.com
993•vismit2000•20h ago•148 comments

Horible public key tricks

https://maurycyz.com/projects/badcert/
149•Curiositry•8h ago•46 comments

Ultorg: The User Interface for Relational Databases

https://www.ultorg.com/
47•Ivoah•4h ago•11 comments

Formalizing CPython

https://broyojo.com/python-formalization/
55•carnevalem•6h ago•23 comments

A failed experiment in laptop cooling

https://kevinboone.me/failed_cooling.html
28•andsoitis•2d ago•25 comments

Semi-transparent, colored cadmium telluride photovoltaic panels in agrivoltaics

https://www.anthropocenemagazine.org/2026/10/magenta-solar-panels-may-be-agrivoltaics-cleverest-t...
308•speckx•18h ago•204 comments

CoreWeave bond yield tops 16% as AI credit stress rises

https://www.cnbc.com/2026/11/06/coreweave-bond-yield-tops-16percent-as-ai-credit-stress-rises.html
135•lxm•5h ago•88 comments

M John Harrison becomes first science fiction author to win the Booker prize

https://www.theguardian.com/books/2026/nov/09/m-john-harrison-the-end-of-everything-wins-2026-boo...
25•sorokod•59m ago•5 comments

Fireworks AI security breach impacts Notion and their customers

https://www.notion.com/help/security-incident-involving-a-third-party-ai-vendor
5•werrett•1h ago•2 comments

The first 300-millimeter power silicon carbide (SiC) wafer

https://www.infineon.com/press-release/2026/infpr202611-028
135•sshah03•14h ago•71 comments

A primer on GPUs and kernel optimization

https://www.nabo.dev/blogs/kernel-primer
142•nomi_uw•4d ago•12 comments

Show HN: Every satellite that passed over any place this week, and its photos

https://www.watched.earth
333•a585gupt•14h ago•57 comments

Muse Ember: Our smallest, most efficient model

https://research.meta.ai/blog/muse-ember
294•dvaplima•14h ago•118 comments

ClickHouse Acquires Xata

https://xata.io/blog/xata-is-joining-clickhouse
10•mebcitto•2h ago•1 comments

Google Gemini routes personal Drive files and emails to human annotators

https://github.com/thisisme6598/gemini_files/
578•gf74918•14h ago•128 comments

Fable 5.2 one-shotted my nephew's dream game

https://notesbylex.com/fable-5-2-one-shotted-my-nephews-dream-game
372•lexandstuff•9h ago•251 comments

Never Gonna Print You Up

https://dixken.de/blog/never-gonna-print-you-up
39•ta988•2d ago•0 comments

On Being an Engineer in 2026

https://twitter.com/shaharglazner/status/2119796029256032278
95•talboren•17h ago•135 comments

Time for AVIF everywhere?

https://www.michaelponders.com/2026/11/isnt-it-time-for-avif-everywhere.html
71•speckx•2d ago•56 comments

Show HN: MeowDisplay Is iPhone Mirroring, but in Reverse

https://meowdisplay.app/
97•raiseCatError•14h ago•37 comments

China drafts lifetime ID codes for every robot it makes, not just humanoids

https://asia-tech-news.ghost.io/china-drafts-lifetime-id-codes-for-every-robot-it-makes-not-just-...
11•ilamont•2d ago•7 comments

Exact – a new cross platform UI framework

https://github.com/expo/exact
116•vmg12•9h ago•81 comments

Parking-app convenience fees in 312 U.S. cities (median $0.35 per session)

https://parkgraph.com/parking-app-fees
77•parkgraph•12h ago•64 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.