frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

I like 'em thick: an apology to my English teachers

https://www.experimental-history.com/p/i-like-em-thick
229•Ariarule•2d ago•75 comments

AliExpress runs silent WebAudio fingerprinting that breaks Bluetooth multipoint

https://blog.laserphile.com/2026/08/aliexpress-webpage-keeping-multipoint.html
641•emctech•7h ago•217 comments

HTML Can Do That

https://chrisburnell.com/html-can-do-that/
251•encyclopedism•1d ago•60 comments

Show HN: I trained a 125M model to autocomplete piano on-device

https://simedw.com/2026/08/20/midi-autocomplete/
345•simedw•5h ago•83 comments

CIA funding helped keep NeXT afloat in the 80s

https://www.wsj.com/tech/steve-jobs-apple-next-cia-161b65f9?st=NWWds1&reflink=desktopwebshare_per...
161•EwanG•17h ago•86 comments

Malicious Rust crate Arrayref runs a build-time payload

https://safedep.io/arrayref-proc-macro1-rust-build-time-malware/
255•abhisek•4h ago•203 comments

Sixtyfour (YC P25) Is Hiring

https://www.ycombinator.com/companies/sixtyfour/jobs/39SkSrA-software-engineering-intern
1•HPMOR•36m ago

Linux 7.2 Released

https://www.igalia.com/2026/08/19/Linux-72-Released.html
32•mariuz•1h ago•1 comments

DiffusionGemma Technical Report

https://arxiv.org/abs/2608.00146
92•gmays•4h ago•14 comments

Clean up Claude 5's token vomit with a separate LLM

https://github.com/zachahn/vomit
83•Bluestein•2h ago•69 comments

How to compromise your system with a job interview

https://www.codedge.de/posts/how-to-compromise-your-system-with-a-job-interview
41•codedge•1h ago•15 comments

Generic Methods in Go 1.27

https://dominik.info/blog/go-generic-methods
26•EspressoGPT•1h ago•5 comments

Xorg-Server 26.0.99.901

https://lists.x.org/archives/xorg-announce/2026-August/003741.html
73•st_goliath•4h ago•24 comments

Hacking with Claude on a $27 Smart Watch

https://www.mikekasberg.com/blog/2026/08/19/hacking-with-claude-on-a-27-smart-watch.html
53•speckx•3h ago•29 comments

Mojo is now open source

https://www.modular.com/blog/mojo-open-source
242•visheshdembla•2d ago•60 comments

An elliptic curve of rank ≥ 30

https://elliptic-rank.icarm.cloud/curve/273
52•robinhouston•3h ago•14 comments

Launch HN: Vendo (YC S26) – Let users build features on top of your product

https://github.com/runvendo/vendo
18•yousefh409•2h ago•8 comments

A theory for decades of C vulnerabilities

https://strawberry9.github.io/the-wrong-memory/Appendix_02.html
26•SilentLambda•3d ago•3 comments

Git at any scale

https://cursor.com/blog/git-at-any-scale
151•meetpateltech•2d ago•23 comments

Anti-AI fonts are useless and harmful

https://blog.yaros.ae/anti-ai-fonts-are-useless-and-harmful/
43•speckx•2h ago•26 comments

Show HN: Open-source Stripe Connect alternative

https://zoneless.com
30•tinyprojects•2h ago•17 comments

Windows brings out the Rorschach test in everyone (2003)

https://devblogs.microsoft.com/oldnewthing/20030825-00/?p=42803
317•luu•11h ago•114 comments

Every Model Cheats

https://dreadnode.io/research/every-model-cheats-prompt-level-mitigation-of-cheating-on-offensive...
42•vga805•3h ago•23 comments

Double-double: 31 digits of precision without leaving the FPU

https://marekfiser.com/blog/double-double-arithmetic/
29•iliketrains•3d ago•4 comments

Show HN: Check if any of the $656M in unclaimed royalties at The MLC is yours

https://pub.doub.ly/
38•knaught•2h ago•20 comments

Nearly 1,400 live streams from Japan

https://tomarigi.me/
65•pajop•2d ago•13 comments

Bun 1.4

https://bun.com/blog/bun-v1.4
169•meetpateltech•3h ago•95 comments

Why the Ocean Cleanup hasn't solved the plastic pollution crisis

https://therevelator.org/why-ocean-cleanup-has-not-solved-plastic-pollution/
72•sohkamyung•4h ago•62 comments

Stop Anthropomorphizing Intermediate Tokens as Reasoning/Thinking Traces

https://arxiv.org/abs/2504.09762
133•nunodonato•1d ago•50 comments

Theory of Fluids Enters the 21st Century

https://www.quantamagazine.org/theory-of-fluids-enters-the-21st-century-20260817/
51•librasteve•3d ago•3 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.