frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Hacking your PC using your speaker without ever touching it

https://blog.nns.ee/2026/06/03/katana-badusb/
346•xx_ns•4h ago•61 comments

Meta workers can opt out of being tracked at work up to 30 min

https://www.bbc.com/news/articles/c93x0k194yno
226•reconnecting•2h ago•184 comments

Every Byte Matters

https://fzakaria.com/2026/06/01/every-byte-matters
133•ingve•3h ago•48 comments

PlayStation Architecture

https://www.copetti.org/writings/consoles/playstation/
116•gregsadetsky•4h ago•20 comments

Nabokov's pale fire: the lost 'father of all hypertext demos'? (2011)

https://dl.acm.org/doi/pdf/10.1145/1995966.1996008
63•aragonite•2d ago•11 comments

1-Click GitHub Token Stealing via a VSCode Bug

https://blog.ammaraskar.com/github-token-stealing/
547•ammar2•23h ago•79 comments

Show HN: Edsger – A handwritten Clojure REPL for the reMarkable 2

https://handwritten.danieljanus.pl/2026-06-01-edsger.html
140•nathell•20h ago•26 comments

I built a ceiling projection mapping of the planes flying over my house

https://old.reddit.com/r/nextfuckinglevel/comments/1tvmcin/i_live_in_the_take_off_path_of_sfo_and...
49•frereubu•1h ago•9 comments

Show HN: I reverse-engineered the world maps of Test Drive III (1990 DOS game)

https://github.com/s-macke/Test-Drive-3-Maps
162•s-macke•3d ago•44 comments

Use your Nvidia GPU's VRAM as swap space on Linux

https://github.com/c0dejedi/nbd-vram
391•tanelpoder•15h ago•101 comments

MAI-Code-1-Flash

https://microsoft.ai/news/introducingmai-code-1-flash/
505•EvanZhouDev•20h ago•236 comments

Piramidal (YC W24) – Software Engineers – NYC Onsite

1•dsacellarius•2h ago

Shopify Is Down

https://www.shopifystatus.com
30•harrouet•53m ago•18 comments

Leiden Declaration on Artificial Intelligence and Mathematics

https://leidendeclaration.ai/
75•zvr•8h ago•24 comments

What I've learned about the trombone

http://bryanhu.com/blog/posts/what-ive-learned-about-the-trombone/
31•bookofjoe•4h ago•25 comments

The Unreasonable Redundancy of Nature's Protein Folds

https://research.ligo.bio/posts/unreasonable-redundancy-of-natural-protein-folds/
136•ray__•11h ago•39 comments

Thomas Mann: Goethe Heartened by Panama (As Suez for English, or Danube-Rhine)

https://yalereview.org/article/thomas-mann-goethe
10•curio_Pol_curio•2d ago•0 comments

Show HN: Tired of duct-taping access control into agent prompts. Here's the fix

https://github.com/yaodub/cast
8•zwigglers•1h ago•6 comments

AI outperforms law professors in Stanford Law study

https://law.stanford.edu/press/ai-outperforms-law-professors-in-stanford-law-study/
343•berlianta•15h ago•291 comments

DIY Bipedal Robot Used Pneumatic "Air-Muscles" Instead of Motors

https://spectrum.ieee.org/shadow-walker-biped-humanoid-robot
51•sohkamyung•3d ago•16 comments

32GB of DDR5 now costs $375 – AI shortage continues to squeeze PC building

https://www.tomshardware.com/pc-components/ddr5/32gb-of-ddr5-now-costs-usd375-minimum-ai-shortage...
103•papersail•2h ago•121 comments

U of T researchers demonstrate AI worm could target any online device

https://www.utoronto.ca/news/u-t-researchers-demonstrate-ai-worm-could-target-any-online-device
89•shscs911•11h ago•30 comments

Pluto.jl 1.0 release – reactive notebook for Julia

https://discourse.julialang.org/t/pluto-1-0-release/137296
186•fons-p•15h ago•27 comments

Roku LT Operating System open source distribution

https://blog.roku.com/developer/roku-lt-os
99•dpmdpm•13h ago•43 comments

Capstone – multi-platform, multi-architecture disassembly framework

https://www.capstone-engine.org/
83•gregsadetsky•12h ago•4 comments

Writing Portable ARM64 Assembly (2023)

https://ariadne.space/2023/04/12/writing-portable-arm-assembly.html
49•luu•2d ago•21 comments

My thoughts after using Clojure for about a month

https://www.acdw.net/clojure/
270•speckx•18h ago•143 comments

How we index images for RAG

https://www.kapa.ai/blog/how-we-index-images-for-rag
182•mooreds•22h ago•23 comments

HP re-releases classic computer science calculator: The HP-16C

https://hpcalcs.com/product/hp-16c-collectors-edition/
193•dm319•19h ago•124 comments

Gmail thinks I'm stupid, so I left

https://moddedbear.com/gmail-thinks-im-stupid-so-i-left
1080•speckx•19h ago•724 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.