frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Codex Security

https://github.com/openai/codex-security
314•bakigul•3h ago•81 comments

Half-Life ported to Mac OS 9

https://mac-classic.com/news/half-life-ported-to-mac-os-9/
126•freediver•3h ago•47 comments

Show HN: I was tired of opening 2 tabs for every HN link, so I made a userscript

https://github.com/twalichiewicz/HNewhere
87•twalichiewicz•2h ago•31 comments

Substack writers, you need a website

https://elizabethtai.com/2026/06/10/substack-writers-you-need-a-website/
395•speckx•7h ago•206 comments

The Difference Between a Button and a Link

https://unplannedobsolescence.com/blog/buttons-vs-links/
12•alexpetros•35m ago•1 comments

Steel Bank Common Lisp version 2.6.7

https://sbcl.org/all-news.html?2.6.7
194•tmtvl•7h ago•80 comments

Kimi K3 Architecture Overview and Notes

https://sebastianraschka.com/blog/2026/kimi-k3-architecture-notes.html
294•ModelForge•8h ago•37 comments

Delayed Gratification – Proud to Be 'Last to Breaking News'

https://www.slow-journalism.com/
231•speerer•8h ago•134 comments

Schools are adding pepper-spraying drones to help combat active shooters

https://www.washingtonpost.com/nation/2026/07/28/schools-are-adding-pepper-spraying-drones-help-c...
13•zdw•1h ago•12 comments

ReFrame – The EPaper Camera

https://reframe.camera/
9•phil294•1h ago•1 comments

The iPhone Upgrade Program is being replaced by Apple Upgrade

https://www.apple.com/shop/iphone/iphone-upgrade-program
135•lkurtz•7h ago•229 comments

Hubbele: Open-source notetaking app for you and your agents

https://www.hubble.md/
7•handfuloflight•36m ago•0 comments

Teach yourself programming in ten years (1998)

https://www.norvig.com/21-days.html
16•vinhnx•2d ago•1 comments

Zig's Incremental Compilation Internals

https://mlugg.co.uk/posts/incremental-compilation-internals/
188•garyhtou•9h ago•132 comments

Lightweight Spring Boot Monitoring Without Prometheus and Grafana

https://pvrlabs.xyz/articles/lightweight-spring-boot-monitoring.html
3•ejboy•15m ago•0 comments

Pacing the frontier

https://www.pacingthefrontier.com/
67•reducesuffering•4h ago•56 comments

Discovering Cryptographic Weaknesses with Claude

https://www.anthropic.com/research/discovering-cryptographic-weaknesses
172•gslin•7h ago•115 comments

The Fabled Flatbreads of Uzbekistan (2015)

https://www.aramcoworld.com/articles/2015/the-fabled-flatbreads-of-uzbekistan
72•jxub•4d ago•51 comments

Show HN: How far do I have to go to run into 100k people?

https://imjasonh.github.io/playground/population-rays/
40•ImJasonH•5d ago•32 comments

Running Kimi K3 on a M1 Max

https://github.com/gavamedia/deltafin
85•tito•3h ago•64 comments

MCP 2026-07-28 Specification: transport going stateless

https://blog.modelcontextprotocol.io/posts/2026-07-28/
96•Eldodi•6h ago•32 comments

New HIV vaccine shows unprecedented success in preclinical study

https://www.lji.org/news-events/news/post/new-hiv-vaccine-shows-unprecedented-success-in-preclini...
554•codebyaditya•11h ago•237 comments

Underwater oxygen loss threatens earth's stability, researchers warn

https://scripps.ucsd.edu/news/underwater-oxygen-loss-threatens-earths-stability-researchers-warn
106•littlexsparkee•2h ago•55 comments

Interview with Boris Cherny [video]

https://www.youtube.com/watch?v=qyPCVqFUyDo
40•knighthacker•1d ago•30 comments

Una GPS smart watch – Repairable, USB-C charging, developer-friendly

https://unawatch.com/
132•pimterry•9h ago•87 comments

Kimi Linear: An Expressive, Efficient Attention Architecture (2025)

https://arxiv.org/abs/2510.26692
273•ronfriedhaber•13h ago•117 comments

Show HN: Manim (3Blue1Brown's animation engine) in the browser via WebGPU

https://studio.academa.ai/
10•sinaatalay•40m ago•1 comments

How Do I Profile eBPF Code?

https://naveensrinivasan.com/posts/2026-07-22-how-do-i-profile-ebpf-code/
109•snaveen•8h ago•6 comments

Show HN: XY – A Fast, composable, GPU-accelerated interactive plotting library

https://github.com/reflex-dev/xy
111•apetuskey•8h ago•41 comments

How to survive boiling water

https://taxa.substack.com/p/how-to-survive-boiling-water
450•cainxinth•4d ago•100 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.