frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Microsoft turns to AWS as GitHub faces AI capacity crunch

https://runtimewire.com/article/microsoft-github-aws-ai-capacity-crunch
35•ilreb•26m ago•6 comments

A backdoor in a LinkedIn job offer

https://roman.pt/posts/linkedin-backdoor/
794•lwhsiao•7h ago•156 comments

Banned Book Library in a Wi-Fi Smart Light Bulb

https://www.richardosgood.com/posts/banned-book-library/
198•sohkamyung•4h ago•83 comments

Iroh 1.0

https://www.iroh.computer/blog/v1
983•chadfowler•12h ago•294 comments

Amazon Announces Multibillion-Dollar Data Center in Missouri

https://www.narracomm.com/amazon-announces-multibillion-dollar-data-center-in-missouri/
55•thelonelyborg•2h ago•24 comments

TinyWind: A pixel pirate sailing game with real wind physics (380k+ kms sailed)

https://tinywind.io
640•tinywind•10h ago•133 comments

Ask HN: Has anyone replaced Claude/GPT with a local model for daily coding?

737•cloudking•12h ago•351 comments

I Love the Computer

https://michaelenger.com/blog/i-love-the-computer/
161•speckx•7h ago•94 comments

Why I email complete strangers

https://www.goodinternetmagazine.com/why-i-email-complete-strangers/
88•karakoram•5h ago•43 comments

Humanity isn't ready for the coming intelligence explosion

https://www.economist.com/by-invitation/2026/06/15/humanity-isnt-ready-for-the-coming-intelligenc...
9•andsoitis•1h ago•14 comments

Cohere's First Model for Developers

https://cohere.com/blog/north-mini-code
29•hmokiguess•4d ago•4 comments

My Homelab AI Dev Platform

https://rsgm.dev/post/ai-dev-platform/
255•rsgm•12h ago•51 comments

Peopleless economy? Not technically impossible

https://gmalandrakis.com/writings/ad-economicum.html
105•l0new0lf-G•6h ago•209 comments

Hetzner Price Adjustment

https://docs.hetzner.com/general/infrastructure-and-availability/price-adjustment/#cloud-servers
352•tuhtah•13h ago•507 comments

The 90-year-old idea behind JEPA models: Canonical Correlation Analysis

https://shonczinner.github.io/posts/embedding-prediction/
9•Anon84•4d ago•0 comments

US battery manufacturing output continues to break records

https://fred.stlouisfed.org/series/IPG33591S
175•epistasis•6h ago•142 comments

Launch HN: Drafted (YC P26) – Models for residential architecture

47•PrimalNick•10h ago•53 comments

What every coder should know about Gamma Correction

https://blog.johnnovak.net/2016/09/21/what-every-coder-should-know-about-gamma/
69•sph•2d ago•21 comments

Fox to buy Roku

https://www.wsj.com/business/deals/fox-roku-deal-f6e564f9
285•thm•14h ago•377 comments

What job interviews taught me about Kubernetes

https://notnotp.com/notes/what-job-interviews-taught-me-about-kubernetes/
106•chmaynard•7h ago•89 comments

How TimescaleDB compresses time-series data

https://roszigit.com/en/blog/timescaledb-compression-hypercore
125•lkanwoqwp•9h ago•15 comments

Reviews have become expensive, rewrites have become cheap

http://ishmeetbindra.com/posts/reviews-have-become-expensive-rewrites-have-become-cheap/
27•arzh2•3h ago•20 comments

Game Engine White Papers Commander Keen

https://forgottenbytes.net/commander_keen.html
168•mfiguiere•9h ago•53 comments

Show HN: Veterinarian turned founder, AI lawn diagnosis

https://grassdx.com/
42•andrewbr•9h ago•44 comments

Salesforce to Acquire Fin (formerly Intercom) for $3.6B

https://www.salesforce.com/news/press-releases/2026/06/15/salesforce-signs-definitive-agreement-t...
284•colesantiago•15h ago•212 comments

Copper transport drug restores memory and clears toxic Alzheimer's proteins

https://www.monash.edu/news/articles/copper-drug-restores-memory-and-clears-toxic-alzheimers-prot...
262•bookofjoe•12h ago•99 comments

Claude Corps

https://www.anthropic.com/news/claude-corps
98•Mustan•9h ago•62 comments

An O(x)Caml book that runs

https://kcsrk.info/ocaml/oxcaml/teaching/nptel/llm/2026/06/13/an-oxcaml-book-that-runs/
32•anirudh24seven•2d ago•12 comments

Show HN: Fata – Spaced repetition to fight skill rot from AI coding

https://fata.dev
85•djoume•4d ago•45 comments

How memory safety CVEs differ between Rust and C/C++

https://kobzol.github.io/rust/2026/06/15/how-memory-safety-cves-differ-between-rust-and-c-cpp.html
114•nicoburns•11h ago•117 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.