frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Claude Fable 5

https://www.anthropic.com/news/claude-fable-5-mythos-5
1724•Philpax•7h ago•1362 comments

Upcoming breaking changes for npm v12

https://github.blog/changelog/2026-06-09-upcoming-breaking-changes-for-npm-v12/
176•plasma•3h ago•51 comments

Ultrafast machine learning on FPGAs via Kolmogorov-Arnold Networks

https://aarushgupta.io/posts/kan-fpga/
149•ag2718•5h ago•19 comments

Making Graphics Like it's 1993

https://staniks.github.io/articles/catlantean-3d-blog-1/
759•sklopec•14h ago•128 comments

If Claude Fable stops helping you, you'll never know

https://jonready.com/blog/posts/claude-fable5-is-allowed-to-sabotage-your-app-if-youre-a-competit...
403•mips_avatar•3h ago•182 comments

RIP software hackathons. Long live the hardware hackathon

https://blog.oscars.dev/posts/rip-software-hackathons-long-live-the-hardware-hackathon/
33•ozcap•2h ago•7 comments

It's Death

https://jesseduffield.com/ITS-DEATH/
29•inatreecrown2•1h ago•0 comments

More Molly Guards

https://unsung.aresluna.org/more-molly-guards/
13•zdw•3d ago•1 comments

CEOs Who Think AI Replaces Their Employees Are Just Bad CEOs

https://www.techdirt.com/2026/06/09/ceos-who-think-ai-replaces-their-employees-are-just-bad-ceos/
390•speckx•6h ago•158 comments

Exif Smuggling

https://github.com/signalblur/exifsmugglingpoc
48•rolph•3h ago•22 comments

A giant star may have destroyed itself in one of the rarest explosions

https://phys.org/news/2026-05-giant-star-destroyed-universe-rarest.html
158•wglb•1d ago•22 comments

Lies We Tell Ourselves About Email Addresses

https://gitpush--force.com/commits/2026/06/lies-we-tell-ourselves-about-email/
21•theanonymousone•1d ago•20 comments

Test-case reducers are underappreciated debugging tools

https://tratt.net/laurie/blog/2026/test_case_reducers_are_underappreciated_debugging_tools.html
78•ltratt•13h ago•10 comments

OpenCV 5 Is Here: The Biggest Leap in Years for Computer Vision

https://opencv.org/opencv-5/
682•ternaus•3d ago•121 comments

Let's Encrypt bans certificate usage in any US sanctioned territory [pdf]

https://letsencrypt.org/documents/LE-SA-v1.7-June-04-2026-diff.pdf
311•piskov•1d ago•251 comments

Show HN: Resonate – Low-latency, high-resolution spectral analysis

https://alexandrefrancois.org/Resonate/
16•arjf•3d ago•8 comments

Flat Datacenter Networks at Scale at Amazon

https://perspectives.mvdirona.com/2026/06/flat-datacenter-networks-at-scale/
84•tanelpoder•21h ago•18 comments

The LD_DEBUG environment variable (2012)

https://bnikolic.co.uk/blog/linux-ld-debug.html
55•tanelpoder•7h ago•1 comments

FCC wants to kill burner phones by forcing telecoms to get all customers' IDs

https://www.404media.co/fcc-wants-to-kill-burner-phones-by-forcing-telecoms-to-get-all-customers-...
432•berlianta•9h ago•271 comments

Show HN: Nucleus – A security-hardened, Nix-native container runtime

https://github.com/sig-id/nucleus
9•0kenx•1h ago•0 comments

Apple decided not to roll out Siri in EU after denied request for exemption

https://www.reuters.com/business/apple-failed-make-its-ai-tool-comply-eu-regulations-eu-commissio...
348•flanged•8h ago•583 comments

Launch HN: Transload (YC P26) – Measuring freight items with CCTV

33•nils_spatial•8h ago•10 comments

Is Grep All You Need? How Agent Harnesses Reshape Agentic Search

https://arxiv.org/abs/2605.15184
119•Anon84•11h ago•53 comments

Biff.core: system composition for Clojure web apps

https://biffweb.com/p/core/
103•jacobobryant•8h ago•21 comments

Show HN: Gravity – interactive solar-system simulator, from Newton to Einstein

https://qunabu.github.io/Gravity/
140•qunabu•13h ago•34 comments

The iPhone's Last Stand?

https://stratechery.com/2026/the-iphones-last-stand/
166•swolpers•14h ago•208 comments

Company Will Add Phone, AirPod, and Smartwatch Trackers to ALPRs

https://www.404media.co/this-company-will-add-phone-airpod-and-smartwatch-trackers-to-license-pla...
84•Cider9986•3h ago•27 comments

Show HN: GentleOS – A pair of hobby OSes for vintage 32-bit and 16-bit PCs

https://github.com/luke8086/gentleos32
93•luke8086•2d ago•91 comments

Ask HN: Are you still using a Vision Pro?

127•y1n0•6h ago•156 comments

Emerge Career (YC S22) Is Hiring a Founding Growth Marketer

https://www.ycombinator.com/companies/emerge-career/jobs/v0S1AEG-founding-growth-marketer
1•gabesaruhashi•12h ago
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.