frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Qwen 3.8

https://twitter.com/Alibaba_Qwen/status/2078759124914098291
618•nh43215rgb•10h ago•454 comments

Show HN: I replaced a $120k bowling center system with $1,600 in ESP32s

327•section33•4h ago•27 comments

What I learned selling 2,500 MIDI recorders: Hardware is not so hard

https://chipweinberger.com/articles/20260719-hardware-is-not-so-hard
330•chipweinberger•8h ago•150 comments

HMD Touch 4G

https://www.hmd.com/en_int/hmd-touch-4g
31•thisislife2•1h ago•33 comments

Claude Code uses Bun written in Rust now

https://simonwillison.net/2026/Jul/19/claude-code-in-bun-in-rust/
293•tosh•9h ago•383 comments

Bananas sprout in Rayleigh Garden UK after 15 years

https://www.bbc.com/news/articles/cvg8edqq5g5o
73•teleforce•5h ago•56 comments

Minecraft: Java Edition now uses SDL3

https://www.minecraft.net/en-us/article/minecraft-26-3-snapshot-4
194•ObviouslyFlamer•7h ago•141 comments

Blender 5.2 LTS

https://www.blender.org/download/releases/5-2/
271•makizar•5d ago•105 comments

OpenAI reduces Codex Model Context Size from 372k to 272k

https://github.com/openai/codex/pull/33972/files
238•AmazingTurtle•11h ago•105 comments

Cagire: Live Coding in Forth

https://cagire.raphaelforment.fr
50•surprisetalk•1w ago•8 comments

UnifiedIR for Julia

https://github.com/JuliaLang/julia/pull/62334
52•vimarsh6739•21h ago•12 comments

Terence McKenna's Mega Bad Trip

https://psychedelics.community/cultural-icons/terence-mckennas-mega-bad-trip
51•Dimmiwoah•4h ago•39 comments

C64 Basic Dungeon Crawler: Goblin Attack (C64 Basic Part 8)

https://retrogamecoders.com/c64-basic-dungeon-part8/
26•ibobev•4h ago•0 comments

Transcribe.cpp

https://workshop.cjpais.com/projects/transcribe-cpp
683•sebjones•18h ago•140 comments

The Last MPEG-4 Visual Patent Has Expired

https://www.phoronix.com/news/Last-MPEG-4-Patent-Expired
55•LorenDB•2h ago•12 comments

Land Atlas – soil, farmability, and crop analysis for land listings

https://land-atlas-production.up.railway.app/welcome
31•L3dge•6d ago•11 comments

The Zen of Parallel Programming

https://smolnero.com/posts/the-zen-of-parallel-programming
6•edgar_ortega•5d ago•0 comments

Infinities, impossibilities, and the man in the white linen suit

https://iain.so/infinities-impossibilities-and-the-man-in-the-white-linen-suit
44•iainharper•5d ago•35 comments

Moonshot AI suspends new subscriptions due to Kimi K3 demand

https://twitter.com/kimi_moonshot/status/2078855608565207130
78•serialx•3h ago•21 comments

Speech Recognition and TTS in less than 500kb

https://github.com/moonshine-ai/moonshine/tree/main/micro
535•petewarden•4d ago•77 comments

Texas Police Spent $4.5M on Four Chevy Tahoes

https://www.thedrive.com/news/how-texas-police-spent-4-5-million-on-four-chevy-tahoes
61•randycupertino•2h ago•33 comments

Neither GCC nor Clang are compliant with standard C++

https://sebsite.pw/w/20260708-badstdcxx.html
19•birdculture•1h ago•12 comments

Codex Resets

https://codex-resets.com/
263•denysvitali•19h ago•174 comments

I joined the IndieWeb, here's what I learned

https://en.andros.dev/blog/0b8e451e/i-joined-the-indieweb-heres-what-i-learned/
97•andros•8h ago•64 comments

Dupes (product clones) took over the world

https://www.vox.com/podcasts/493930/dupe-culture-fender-ugg-quince-tiktok-amazon-online-shopping
25•gumby•5d ago•22 comments

Less Is More: Why Audio on SoundCloud Looks Different

https://developers.soundcloud.com/blog/less-is-more-why-soundcloud-low-passes-its-aac-transcodings/
13•1317•1h ago•2 comments

Mathematicians still don't know the fastest way to multiply numbers

https://www.scientificamerican.com/article/mathematicians-still-dont-know-the-fastest-way-to-mult...
195•beardyw•6d ago•107 comments

Better and Cheaper Than IPTV

https://github.com/stupside/castor
295•xonery•18h ago•91 comments

Hardcore IndieWeb: Run your own website 100% independently for only $0.01/day

https://www.neatnik.net/hardcore-indieweb
230•cdrnsf•21h ago•183 comments

The death and rebirth of my home server

https://sgt.hootr.club/blog/home-server-rebirth/
87•steinuil•8h ago•65 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.