frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Deutsche Telekom is violating Net Neutrality

https://netzbremse.de/en/
31•tietjens•1h ago•2 comments

Google confirms 'high-friction' sideloading flow is coming to Android

https://www.androidauthority.com/google-sideloading-android-high-friction-process-3633468/
160•_____k•5d ago•69 comments

Adoption of EVs tied to real-world reductions in air pollution: study

https://keck.usc.edu/news/adoption-of-electric-vehicles-tied-to-real-world-reductions-in-air-poll...
365•hhs•9h ago•293 comments

BirdyChat becomes first European chat app that is interoperable with WhatsApp

https://www.birdy.chat/blog/first-to-interoperate-with-whatsapp
567•joooscha•14h ago•346 comments

A Lament for Aperture

https://ikennd.ac/blog/2026/01/old-man-yells-at-modern-software-design/
75•firloop•4d ago•17 comments

David Patterson: Challenges and Research Directions for LLM Inference Hardware

https://arxiv.org/abs/2601.05047
57•transpute•6h ago•3 comments

Two Weeks Until Tapeout

https://essenceia.github.io/projects/two_weeks_until_tapeout/
107•client4•8h ago•5 comments

Intrinsically stretchable 2D MoS2 transistors

https://www.nature.com/articles/s41467-026-68504-2
3•bookofjoe•4d ago•0 comments

Postmortem: Our first VLEO satellite mission (with imagery and flight data)

https://albedo.com/post/clarity-1-what-worked-and-where-we-go-next
173•topherhaddad•13h ago•57 comments

Show HN: AutoShorts – Local, GPU-accelerated AI video pipeline for creators

https://github.com/divyaprakash0426/autoshorts
7•divyaprakash•1h ago•1 comments

Claude Code's new hidden feature: Swarms

https://twitter.com/NicerInPerson/status/2014989679796347375
398•AffableSpatula•18h ago•275 comments

Second Win11 emergency out of band update to address disastrous Patch Tuesday

https://www.windowscentral.com/microsoft/windows-11/windows-11-second-emergency-out-of-band-updat...
140•speckx•6h ago•85 comments

Typography on Pencils (2023)

https://www.presentandcorrect.com/blogs/blog/typography-on-pencils-1-5
66•NaOH•4d ago•3 comments

Raspberry Pi Drag Race: Pi 1 to Pi 5 – Performance Comparison

https://the-diy-life.com/raspberry-pi-drag-race-pi-1-to-pi-5-performance-comparison/
167•verginer•15h ago•81 comments

Like digging 'your own grave': The translators grappling with losing work to AI

https://www.cnn.com/2026/01/23/tech/translation-language-jobs-ai-automation-intl
25•myk-e•1h ago•17 comments

What Ralph Wiggum loops are missing

https://xr0am.substack.com/p/what-ralph-wiggum-loops-are-missing
21•xR0am•4h ago•9 comments

We X-Rayed a Suspicious FTDI USB Cable

https://eclypsium.com/blog/xray-counterfeit-usb-cable/
134•aa_is_op•9h ago•53 comments

Memory layout in Zig with formulas

https://raymondtana.github.io/math/programming/2026/01/23/zig-alignment-and-sizing.html
108•raymondtana•17h ago•25 comments

Nvidia-smi hangs indefinitely after ~66 days

https://github.com/NVIDIA/open-gpu-kernel-modules/issues/971
160•tosh•6h ago•33 comments

The Temporal Consistency Challenge in Video Restoration

https://blog.videowatermarkremove.com/the-temporal-consistency-challenge-from-optical-flow-to-spa...
14•ilmj8426•4d ago•2 comments

Show HN: VM-curator – a TUI alternative to libvirt and virt-manager

https://github.com/mroboff/vm-curator
28•theYipster•5h ago•2 comments

Small Kafka: Tansu and SQLite on a free t3.micro

https://blog.tansu.io/articles/broker-aws-free-tier
85•rmoff•4d ago•16 comments

Ask HN: Gmail spam filtering suddenly marking everything as spam?

171•goopthink•17h ago•112 comments

Maze Algorithms (2017)

http://www.jamisbuck.org/mazes/
131•surprisetalk•1d ago•30 comments

Poland's energy grid was targeted by never-before-seen wiper malware

https://arstechnica.com/security/2026/01/wiper-malware-targeted-poland-energy-grid-but-failed-to-...
224•Bender•12h ago•89 comments

First Design Engineer Hire – Build Games at Gym Class (YC W22)

https://www.ycombinator.com/companies/gym-class-by-irl-studios/jobs/ywXHGBv-design-engineer-senio...
1•hackerews•12h ago

Shared Claude: A website controlled by the public

https://sharedclaude.com/
63•reasonableklout•1d ago•22 comments

Agent orchestration for the timid

https://substack.com/inbox/post/185649875
104•markferree•14h ago•26 comments

Understanding Rust Closures

https://antoine.vandecreme.net/blog/rust-closures/
53•avandecreme•14h ago•23 comments

I built a 2x faster lexer, then discovered I/O was the real bottleneck

https://modulovalue.com/blog/syscall-overhead-tar-gz-io-performance/
11•modulovalue•4d ago•6 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•8mo 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•8mo 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.