frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

AWS: Inaccurate Estimated Billing Data – $1.7 billion

680•nprateem•8h ago•387 comments

First atmosphere found on Earth-like planet in habitable zone of distant star

https://www.bbc.com/news/articles/cy4kdd1e0ejo
168•neversaydie•4h ago•122 comments

Mozilla: The state of open source AI

https://stateofopensource.ai/
223•rellem•3h ago•149 comments

A Road to Lisp: Which Lisp

https://scotto.me/blog/2026-07-17-which-lisp/
102•silcoon•4h ago•57 comments

Kimi K3, and what we can still learn from the pelican benchmark

https://simonwillison.net/2026/Jul/16/kimi-k3/
97•droidjj•3h ago•51 comments

AI Meets Cryptography 2: What AI Found in OpenVM's ZkVM

https://blog.zksecurity.xyz/posts/openvm-bugs/
55•duha•3h ago•0 comments

Three ways people respond to a problem (other than solving it)

https://improvesomething.today/responses-to-problems/
92•surprisetalk•4h ago•35 comments

Frame – the first Linux Assembly X server

https://isene.org/2026/07/Frame.html
31•guybedo•2h ago•12 comments

Show HN: Watch bots interact with an SSH honeypot in real time

https://honeypotlive.cc/
85•tusksm•4h ago•35 comments

Frank Lloyd Wright's First Home

https://www.architecturaldigest.com/story/frank-lloyd-wright-home-and-studio-everything-you-need-...
17•NaOH•4d ago•3 comments

Show HN: Explore the Workspaces of Modern Creators

https://workspaces.xyz/
31•ryangilbert•2h ago•24 comments

More Bounce to the Ounce

https://mceglowski.substack.com/p/more-bounce-to-the-ounce
57•pavel_lishin•4h ago•14 comments

EEG shows brain can simultaneous encode two speech streams

https://journals.plos.org/plosbiology/article?id=10.1371/journal.pbio.3003876
221•giuliomagnifico•12h ago•141 comments

Apple targets dozens of OpenAI employees with legal letters

https://www.ft.com/content/1b8c9d52-88a9-426b-ba47-f1811f859166
276•merksittich•6h ago•223 comments

Designing emoji for the way we communicate today

https://blog.google/products-and-platforms/platforms/android/world-emoji-day-noto-3d/
10•pentagrama•1h ago•3 comments

Manufact (YC S25) Is Hiring a Senior infra engineer to build the MCP cloud

https://www.ycombinator.com/companies/manufact/jobs/Dh6PYP5-senior-infrastructure-engineer
1•luigipederzani•4h ago

Claude Code: Anatomy of a Misfeature

https://www.olafalders.com/2026/07/17/claude-code-anatomy-of-a-misfeature/
116•oalders•3h ago•78 comments

Pebble Mega Update – July 2026

https://repebble.com/blog/pebble-mega-update-july-2026
231•crazysaem•14h ago•145 comments

Faster binary search: from compiled code to mechanical sympathy

https://pythonspeed.com/articles/branchless-binary-search/
35•enz•5d ago•10 comments

Short sellers notch $8.7B profit as SpaceX shares dip to IPO price

https://www.reuters.com/business/media-telecom/short-sellers-rack-up-87-bln-profit-spacex-slips-b...
55•1vuio0pswjnm7•2h ago•12 comments

VulnHunter: Capital One's agentic AI code security tool

https://www.capitalone.com/tech/open-source/announcing-vulnhunter/
35•medina•5h ago•25 comments

PennyLane is an open-source quantum software platform for quantum

https://github.com/PennyLaneAI/pennylane
32•donutloop•4h ago•4 comments

Microsoft Comic Chat is now open source

https://opensource.microsoft.com/blog/2026/07/16/microsoft-comic-chat-is-now-open-source/
773•jervant•1d ago•165 comments

Camera Chase Vehicle

https://transistor-man.com/gimbal_camera_rover.html
146•geerlingguy•1w ago•14 comments

Show HN: Simulator for a custom 8-bit discreet logic computer

https://msap2.mehran.dk
12•mehrant•3d ago•2 comments

Decoy Font

https://www.mixfont.com/experiments/decoy-font
657•ray__•1d ago•147 comments

Kimi K3: Open Frontier Intelligence

https://www.kimi.com/blog/kimi-k3
1923•vincent_s•1d ago•1125 comments

How Has Roman Concrete Lasted for Millennia? 1,900-Year-Old Latrine Offers Clues

https://www.smithsonianmag.com/smart-news/how-has-roman-concrete-lasted-for-millennia-a-1900-year...
237•divbzero•14h ago•187 comments

Tannakian Reconstruction

https://bartoszmilewski.com/2026/07/14/tannakian-reconstruction/
20•ibobev•3d ago•1 comments

An Engineer's Guide to USB Typе-С (2024)

https://www.ti.com/lit/eb/slyy228/slyy228.pdf?ts=1759892558029
269•gregsadetsky•1w ago•55 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.