frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

OverpAId – Fire your CEO. Hire the future

https://overpaid.lol
443•ignaloidas•3h ago•203 comments

Back to Kagi

https://blog.melashri.net/micro/back-to-kagi/
82•speckx•1h ago•56 comments

Businesses with ugly AI menu redesigns

https://blog.fiddery.com/businesses-with-ugly-ai-menu-redesigns/
73•speckx•1h ago•39 comments

Why Do You Suck at Juggling?

https://pgadey.ca/notes/suck-at-juggling/
17•surprisetalk•1w ago•10 comments

OpenAI and Hugging Face address security incident during model evaluation

https://openai.com/index/hugging-face-model-evaluation-security-incident/
1377•mfiguiere•18h ago•929 comments

Introduction to Formal Verification with Lean Part 1

https://hashcloak.com/blog/tutorial-introduction-to-formal-verification-with-lean-(part-1)
131•badcryptobitch•2d ago•15 comments

Kimi K3 Is Competitive with Fable; Kimi K3 and Fable Is SoTA

https://fireworks.ai/blog/kimik3-fable
763•piotrgrabowski•15h ago•397 comments

Intel Starts Shipping High-NA EUV Silicon

https://morethanmoore.substack.com/p/intel-starts-shipping-high-na-euv
153•zdw•3d ago•59 comments

10 REM"_(C2SLFF4

https://beej.us/blog/data/mystery-comment/
28•ingve•2h ago•4 comments

Cornell's Interactive Wall of Birds

https://academy.allaboutbirds.org/features/wallofbirds/?_hsmi=428996456
22•yareally•3d ago•4 comments

Original Apollo 11 Guidance Computer source code for command and lunar modules

https://github.com/chrislgarry/Apollo-11
119•noteness•8h ago•36 comments

Advertise in ChatGPT

https://ads.openai.com/
943•montecarl•19h ago•720 comments

FreeInk: Open ecosystem for e-readers

https://freeink.org/
644•FriedPickles•19h ago•132 comments

Judge approves $1.5B Anthropic settlement for pirated books used to train Claude

https://apnews.com/article/ai-anthropic-copyright-settlement-claude-books-bartz-74b140444023898ae...
467•BeetleB•19h ago•437 comments

AMD Ryzen 7 7700X3D Review: 3D V-Cache Gaming Performance for Less – HotHardware

https://hothardware.com/reviews/amd-ryzen-7-7700x3d-gaming-cpu-review
33•rbanffy•3d ago•32 comments

Gemini 3.6 Flash, 3.5 Flash-Lite, and 3.5 Flash Cyber

https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-3-6-flash-3-5-flas...
726•logickkk1•22h ago•544 comments

Late.sh – a command-line Clubhouse for computer people

https://late.sh/
245•itherseed•11h ago•86 comments

A digestion of the Jacobian conjecture counterexample

https://terrytao.wordpress.com/2026/07/21/a-digestion-of-the-jacobian-conjecture-counterexample/
288•jeremyscanvic•17h ago•118 comments

ScreenWall – Turn old phones into synced widgets for your space

https://screenwall.app/
65•buibuibui•5d ago•26 comments

Ten Steps Towards Happiness (2015)

http://hintjens.com/blog:99
181•emerongi•12h ago•75 comments

Never Enough

https://dark.ronacher.eu/2026/7/21/never-enough/
102•reasonableklout•10h ago•34 comments

Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting

https://runtimewire.com/article/jack-dorsey-block-buzz-team-chat-ai-agents-git
346•ryanmerket•20h ago•306 comments

"Drawing" the Mona Lisa with GPT-5.6, Claude, Gemini, and Grok

https://www.tryai.dev/blog/ai-drawing-arena-colored-pencils-claude-gpt-grok
227•hershyb_•16h ago•80 comments

Long presumed dead, a thriving coral reef is discovered in West Africa

https://e360.yale.edu/digest/benin-coral-reef
369•speckx•22h ago•84 comments

Apple defeats liability for not scanning iCloud for CSAM

https://blog.ericgoldman.org/archives/2026/07/apple-defeats-liability-for-not-scanning-icloud-for...
436•speckx•23h ago•471 comments

It's a shame what's happened to radio

https://blog.jimgrey.net/2026/07/21/its-a-shame-whats-happened-to-radio-3/
162•sonicrocketman•14h ago•179 comments

Overload and insight look identical from the outside

https://pilgrima.ge/p/what-the-wire-knows
10•momentmaker•3d ago•0 comments

Laguna S 2.1

https://poolside.ai/blog/introducing-laguna-s-2-1
372•rexledesma•20h ago•69 comments

Map of the world's great castles and fortresses

https://thecastlemap.com/
286•marklit•22h ago•180 comments

Gemini last models: temperature, top_p, and top_k are deprecated and ignored

https://ai.google.dev/gemini-api/docs/latest-model
113•greatgib•16h ago•39 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.