Recent submissions

Comment · 4 months ago
> Inspect proteins, alignments, genomic tracks, chemical structures, and PDFs in their native form, with no extra installation required.

I like how this implies parsing PDFs is as hard as like protein folding

Comment · 4 months ago
Surprised no one's built a BIOS MCP yet
Comment · 5 months ago
Is that better? I'd much rather have someone trying to build a good product to sell to willing buyers at a fair price than some zealot who thinks he's going to usher in the second coming and end the world or something.
Comment · 6 months ago
I'm sorry because I love the scratch project but this has to be said: they found XSS in SVGs in a surface with attacker-controlled access to Node and their fix was sanitizing it using regex??? And this was discovered by a user on scratch?

Even worse, OP's latest post "Every version of Scratch is vulnerable to arbitrary code execution" just tells you how exactly to exploit something similar today in the current version with no mention of responsible disclosure except a plug to say, "hey, check out my project, this one doesn't have RCE!" This is so irresponsible it borders on malicious.

Comment · 6 months ago
Valuations are based on future expected earnings, not revenue. It cost Ford a lot of money to make that $60k car. The margins for AI companies are unknown but the market is pricing that they’ll be higher at one point. Not that they’ll attract more revenue from the average person.
Comment · 6 months ago
On the other hand, I can ask codex “what would an implementation of X look like” and it talks to me about it versus Claude just going out and writing it without asking. Makes me like codex way more. There’s an inherent war of incentives between coding agents and general purpose agents.
Comment · 7 months ago
Compilers are very good these days. If it has no side effects it will likely be compiled out.
Comment · 7 months ago
If your assert compiles down to `if (condition) {}` in production then the compiler will optimize away the condition while keeping any side effects.
Comment · 7 months ago
Brilliant
Comment · 7 months ago
I will never stop hating on the orphan rule, a perfect summary of what’s behind a lot of rust decisions. Purism and perfectionism at the cost of making a useful language, no better way to torpedo your ecosystem and make adding dependencies really annoying for no reason. Like not even a —dangerously-disable-the-orphan-rule, just no concessions here.
Comment · 7 months ago
Claude is secretly conditioning everyone to use —-dangerously-skip-permissions so it can flip a switch one day and start a botnet
Comment · 7 months ago
Rust is the wrong language for effects ironically because of its strict typing. They would probably decide that all effects have to be specified on every function or that any change in capabilities is a breaking change. Which is safest, but horrible for dev ex. Whereas Go most people would just be like “yeah, Hyrum’s law, sorry I broke your weird effect consumer, I don’t really care.”
Comment · 8 months ago
But that doesn't translate to paying Gemini customers
Comment · 8 months ago
This is really good! I like how it reads like a blog post, it feels like I'm learning a skill on how to write good skills. Maybe that's another heuristic, a skill should read like an interesting blog post, highlighting non-obvious information.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton