frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Show HN: Kakehashi – Experimental userspace to run macOS binaries on Linux ARM

https://github.com/wie-project/kakehashi
70•vlad_kalinkin•2h ago•24 comments

Developers are attached to tools because tools encode trust

https://stackoverflow.blog/2026/07/29/developers-are-attached-to-tools-because-tools-encode-trust/
37•HieronymusBosch•4d ago•9 comments

How the words we teach English language learners changed

https://pudding.cool/2026/07/essential-words/
129•c-oreills•3h ago•74 comments

Harvesting SSH Credentials: Insights from My Honeypot Network

https://uphillsecurity.com/articles/harvesting-ssh-credentials-insights-from-my-honeypot-network/
11•whatbackup•1h ago•5 comments

Rooting, firmware analysis and persistent credentials of TP-Link TL-841N

https://blog.juni-mp4.com/posts/42/rooting-the-tplink-tl841n-pt1/
36•mindracer•2h ago•1 comments

Show HN: NixOS-DGX-Spark – Nix and NixOS on the DGX Spark

https://github.com/graham33/nixos-dgx-spark
35•graham33•1h ago•7 comments

Twenty Years of RISC OS Open

https://www.riscosopen.org/news/articles/2026/06/20/twenty-years-of-risc-os-open
114•AlexeyBrin•6h ago•20 comments

F*: A general-purpose proof-oriented programming language

https://fstar-lang.org/
104•ducktective•6h ago•34 comments

Meshdiff – visually compare two STL versions in the browser, client-side

https://meshdiff.com/
145•projscope•7h ago•13 comments

Karpathy’s Pelican

https://twitter.com/karpathy/status/2083749667410727319
162•delichon•14h ago•138 comments

Fasttracker II clone in C using SDL 2

https://16-bits.org/ft2.php
73•andsoitis•4d ago•25 comments

Folding Paper Globes

https://foldingglobes.com/globes
104•dango2506•4d ago•18 comments

When transit passes were designed by hand (2022)

https://letterformarchive.org/news/milwaukee-transit-passes/
49•nate•2d ago•16 comments

Show HN: Bor – Open-source policy management for Linux desktops

https://getbor.dev/blog/2026-08-02-bor-v080-release/
143•eniac111•9h ago•19 comments

Turtle-inspired interactive Python project

https://www.codembark.com/projects/fv20lz9map/spider-web-drawing
7•camdenreslink•5d ago•0 comments

Show HN: Fuse – statically typed functional programming language

https://fuselang.org
79•the_unproven•7h ago•15 comments

Rust All Hands 2026 Retrospective

https://blog.rust-lang.org/inside-rust/2026/07/31/all-hands-2026-retrospective/
66•dcminter•8h ago•28 comments

Artificial Intelligence: Ars Notoria and the Promise of Instant Knowledge

https://publicdomainreview.org/essay/ars-notoria/
99•jruohonen•8h ago•25 comments

Great Question (YC W21) Is Hiring Senior Demand Gen Manager

https://www.ycombinator.com/companies/great-question/jobs/YutDxyf-senior-demand-generation-manager
1•nedwin•6h ago

Go 1.27 Interactive Tour

https://victoriametrics.com/blog/go-1-27/index.html
328•Hixon10•17h ago•160 comments

Show HN: I'm a 15 Year Old Wannabe Engineer, This Is a Cycloidal Gearbox I Built

https://github.com/tom-ilan/cycloidal_gearbox
285•tomilan•16h ago•94 comments

Pushes to arch AUR are suspendended right now.

https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/message/YPJ3FQYJTJXXY3R...
40•EbNar•1h ago•16 comments

Holocloth

https://holocloth.vercel.app
127•ingve•2d ago•24 comments

Diátaxis

https://diataxis.fr/
483•ryanseys•22h ago•56 comments

Microsoft raises Xbox prices by up to 43%

https://www.theverge.com/games/974253/xbox-prices-increasing-200-euros
5•BlueBerry2001•7m ago•0 comments

Norway Salmon

https://www.abc.net.au/news/2026-07-28/how-norway-s-salmon-industry-became-a-global-behemoth/1069...
90•CHB0403085482•5d ago•56 comments

MkLinux and the pimped-out Apple Workgroup Server 9150

http://oldvcr.blogspot.com/2026/08/mklinux-and-pimped-out-apple-workgroup.html
97•goldenskye•15h ago•13 comments

A Rant About “Technology” (2005)

https://www.ursulakleguin.com/a-rant-about-technology
117•jamesgill•4h ago•65 comments

ESP32-C3 SuperMini antenna modification

https://peterneufeld.wordpress.com/2025/03/04/esp32-c3-supermini-antenna-modification/
63•ta988•12h ago•11 comments

Show HN: Syncular – offline-first SQL sync with TypeScript and Rust cores

https://github.com/syncular/syncular
67•quambo•9h ago•23 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.