frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

How I use Claude Code: Separation of planning and execution

https://boristane.com/blog/how-i-use-claude-code/
489•vinhnx•8h ago•301 comments

Japanese Woodblock Print Search

https://ukiyo-e.org/
87•curmudgeon22•5h ago•15 comments

How Taalas "prints" LLM onto a chip?

https://www.anuragk.com/blog/posts/Taalas.html
104•beAroundHere•14h ago•46 comments

A Botnet Accidentally Destroyed I2P

https://www.sambent.com/a-botnet-accidentally-destroyed-i2p-the-full-story/
100•Cider9986•8h ago•55 comments

Two Bits Are Better Than One: making bloom filters 2x more accurate

https://floedb.ai/blog/two-bits-are-better-than-one-making-bloom-filters-2x-more-accurate
89•matheusalmeida•4d ago•15 comments

Show HN: Llama 3.1 70B on a single RTX 3090 via NVMe-to-GPU bypassing the CPU

https://github.com/xaskasdf/ntransformer
234•xaskasdf•12h ago•55 comments

How far back in time can you understand English?

https://www.deadlanguagesociety.com/p/how-far-back-in-time-understand-english
522•spzb•3d ago•279 comments

Gamedate – A site to revive dead multiplayer games

https://gamedate.org/
92•msuniverse2026•1d ago•10 comments

Evidence of the bouba-kiki effect in naïve baby chicks

https://www.science.org/doi/10.1126/science.adq7188
126•suddenlybananas•11h ago•35 comments

Parse, Don't Validate and Type-Driven Design in Rust

https://www.harudagondi.space/blog/parse-dont-validate-and-type-driven-design-in-rust/
184•todsacerdoti•13h ago•45 comments

zclaw: personal AI assistant in under 888 KB, running on an ESP32

https://github.com/tnm/zclaw
164•tosh•20h ago•88 comments

Claws are now a new layer on top of LLM agents

https://twitter.com/karpathy/status/2024987174077432126
290•Cyphase•1d ago•728 comments

CXMT has been offering DDR4 chips at about half the prevailing market rate

https://www.koreaherald.com/article/10679206
196•phront•18h ago•183 comments

Scientists discover recent tectonic activity on the moon

https://phys.org/news/2026-02-scientists-tectonic-moon.html
47•bookmtn•4d ago•3 comments

Toyota Mirai hydrogen car depreciation: 65% value loss in a year

https://carbuzz.com/toyota-mirai-massive-depreciation-one-year/
142•iancmceachern•15h ago•319 comments

Show HN: Minimalist Glitch Art Maker (100% client-side)

https://yuyz0112.github.io/glitch-art-maker/
6•yz-yu•5d ago•0 comments

Coccinelle: Source-to-source transformation tool

https://github.com/coccinelle/coccinelle
95•anon111332142•1d ago•28 comments

Canvas_ity: A tiny, single-header <canvas>-like 2D rasterizer for C++

https://github.com/a-e-k/canvas_ity
93•PaulHoule•14h ago•34 comments

Carelessness versus Craftsmanship in Cryptography

https://blog.trailofbits.com/2026/02/18/carelessness-versus-craftsmanship-in-cryptography/
22•ingve•3d ago•1 comments

I verified my LinkedIn identity. Here's what I handed over

https://thelocalstack.eu/posts/linkedin-identity-verification-privacy/
1260•ColinWright•1d ago•433 comments

The Human Root of Trust – public domain framework for agent accountability

https://humanrootoftrust.org/
14•3du4rd0v3g4•19h ago•5 comments

A16z partner says that the theory that we’ll vibe code everything is wrong

https://www.aol.com/articles/a16z-partner-says-theory-well-050150534.html
131•paulpauper•1d ago•195 comments

Keep Android Open

https://f-droid.org/2026/02/20/twif.html
2063•LorenDB•1d ago•695 comments

EDuke32 – Duke Nukem 3D (Open-Source)

https://www.eduke32.com/
187•reconnecting•13h ago•65 comments

Inputlag.science – Repository of knowledge about input lag in gaming

https://inputlag.science
87•akyuu•13h ago•18 comments

What not to write on your security clearance form (1988)

https://milk.com/wall-o-shame/security_clearance.html
442•wizardforhire•16h ago•194 comments

Permacomputing

https://wiki.xxiivv.com/site/permacomputing.html
140•tosh•4d ago•35 comments

Finding forall-exists Hyperbugs using Symbolic Execution

https://dl.acm.org/doi/full/10.1145/3689761
39•todsacerdoti•5d ago•2 comments

Don't create .gitkeep files, use .gitignore instead (2023)

https://adamj.eu/tech/2023/09/18/git-dont-create-gitkeep/
141•frou_dh•1d ago•82 comments

AI uBlock Blacklist

https://github.com/alvi-se/ai-ublock-blacklist
245•rdmuser•1d ago•110 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•9mo ago

Comments

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