frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Gentoo Linux 2025 Review

https://www.gentoo.org/news/2026/01/05/new-year.html
124•akhuettel•4h ago•41 comments

Happy 50th Birthday KIM-1

https://github.com/netzherpes/KIM1-Demo
19•JKCalhoun•1h ago•2 comments

"Food JPEGs" in Super Smash Bros. & Kirby Air Riders

https://sethmlarson.dev/food-jpegs-in-super-smash-bros-and-kirby-air-riders
110•SethMLarson•4d ago•25 comments

C++ std::move doesn't move anything: A deep dive into Value Categories

https://0xghost.dev/blog/std-move-deep-dive/
150•signa11•2d ago•105 comments

Think of Pavlov

https://boz.com/articles/think-pavlov
59•kiyanwang•4h ago•19 comments

I dumped Windows 11 for Linux, and you should too

https://www.notebookcheck.net/I-dumped-Windows-11-for-Linux-and-you-should-too.1190961.0.html
229•smurda•4h ago•230 comments

BasiliskII Macintosh 68k Emulator Ported to ESP32-P4 / M5Stack Tab5

https://github.com/amcchord/M5Tab-Macintosh
31•rcarmo•3h ago•1 comments

Instagram data breach reportedly exposed the personal info of 17.5M users

https://www.engadget.com/cybersecurity/an-instagram-data-breach-reportedly-exposed-the-personal-i...
24•IvanAchlaqullah•36m ago•4 comments

The Concise TypeScript Book

https://github.com/gibbok/typescript-book
152•javatuts•10h ago•32 comments

Vojtux – Unofficial Linux Distribution Aimed at Visually Impaired Users

https://github.com/vojtapolasek/vojtux
89•TheWiggles•4d ago•25 comments

My Home Fibre Network Disintegrated

https://alienchow.dev/post/fibre_disintegration/
185•alienchow•11h ago•168 comments

HTML-only conditional lazy loading (via preload and media)

https://orga.cat/blog/html-conditional-lazy-loading/
33•netol•4h ago•4 comments

Show HN: Porting xv6 to HiFive Unmatched board

https://github.com/eyengin/xv6-riscv-unmatched
11•eyengin•1d ago•0 comments

You are not required to close your <p>, <li>, <img>, or <br> tags in HTML

https://blog.novalistic.com/archives/2017/08/optional-end-tags-in-html/
61•jen729w•1d ago•91 comments

More than one hundred years of Film Sizes

https://wichm.home.xs4all.nl/filmsize.html
64•exvi•7h ago•17 comments

Learning from Sudoku Solvers (2007)

http://ravimohan.blogspot.com/2007/04/learning-from-sudoku-solvers.html
4•forks•5d ago•1 comments

Finding and fixing Ghostty's largest memory leak

https://mitchellh.com/writing/ghostty-memory-leak-fix
531•thorel•20h ago•119 comments

Show HN: I used Claude Code to discover connections between 100 books

https://trails.pieterma.es/
424•pmaze•22h ago•130 comments

Show HN: Ferrite – Markdown editor in Rust with native Mermaid diagram rendering

https://github.com/OlaProeis/Ferrite
204•OlaProis•13h ago•117 comments

Code and Let Live

https://fly.io/blog/code-and-let-live/
388•usrme•1d ago•144 comments

CPU Counters on Apple Silicon: article + tool

https://blog.bugsiki.dev/posts/apple-pmu/
127•verte_zerg•4d ago•0 comments

Outward Signs of Inner Mysteries

https://lareviewofbooks.org/article/outward-signs-of-inner-mysteries/
10•prismatic•4d ago•0 comments

'Bandersnatch': The Works That Inspired the 'Black Mirror' Interactive Feature (2019)

https://www.hollywoodreporter.com/tv/tv-news/black-mirror-bandersnatch-real-life-works-influences...
60•rafaepta•5d ago•24 comments

Iran Shuts Down Starlink Internet for First Time

https://www.forbes.com/sites/zakdoffman/2026/01/11/kill-switch-iran-shuts-down-starlink-internet-...
141•neom•3h ago•80 comments

Google: Don't make "bite-sized" content for LLMs

https://arstechnica.com/google/2026/01/google-dont-make-bite-sized-content-for-llms-if-you-care-a...
43•cebert•3h ago•25 comments

Open Chaos: A self-evolving open-source project

https://www.openchaos.dev/
398•stefanvdw1•23h ago•82 comments

Max Payne – two decades later – Graphics Critique (2021)

https://darkcephas.blogspot.com/2021/07/max-payne-two-decades-later-graphics.html
98•davikr•11h ago•30 comments

AI is a business model stress test

https://dri.es/ai-is-a-business-model-stress-test
290•amarsahinovic•22h ago•276 comments

A Year of Work on the Arch Linux Package Management (ALPM) Project

https://devblog.archlinux.page/2026/a-year-of-work-on-the-alpm-project/
89•susam•13h ago•24 comments

Don't fall into the anti-AI hype

https://antirez.com/news/158
254•todsacerdoti•5h ago•364 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•8mo ago

Comments

tonyarkles•8mo 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•8mo ago
You can convert edge coloring problems into vertex coloring problems and vice versa through a simple O(n) procedure.
meindnoch•8mo 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•7mo ago
Indeed. Thanks, I stand corrected.
tonyarkles•8mo 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•8mo 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•8mo 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•8mo ago
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•8mo 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•8mo 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•7mo 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.
phkahler•8mo ago
Is this going to lead to faster compile times? Faster register allocation...
john-h-k•8mo ago
Very few compilers actually use vertex coloring for register allocation
isaacimagine•8mo 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•8mo ago
and this post isn't even about vertex coloring
DannyBee•8mo 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.