There is even a table copy-pasted into a paragraph without noticing.

> What’s needed is something different:

> Requirement ptrace seccomp eBPF Binary rewrite Low overhead per syscall No (~10-20µs) Yes Yes Yes [...]

null hypothesis bot

Reminding me of the Shoelace [0] project, which was rebranded as Web Awesome. The original (v2) repository was then archived.

[0]: https://shoelace.style/

The watch is interactive! Nice detail

Productivity is finite. If you pivot entirely to the AI stack, you're going to lose bandwidth for everything else. It's an opportunity cost problem.

A better example would be to use LLMs to generate passwords or secret keys. Then even if it looks random to human, the inherent bias would make it a security disaster.

You can still obfuscate JS heavily and make a VM that executes also obfuscated code calling arbitrary browser APIs. At least In WASM everything is sandboxed so the attack surface is smaller.

cf. Kagi is a good take

Remember: It is a company that keep saying how much production code can be written by AI in xx years, but at the same time recruiting new engineers.

The "source" link at the footer seems to point to the author's GitHub profile, not source repository. The repo under it contains no code either.

Sorry don't take this personally but isn't this made with LLMs? Isn't the "incident with Tailwind" the problem that devs no longer support the project because they use it through LLMs often without knowing?

I mean if i understand you are saying you won't release open source code because LLMs would feed/stole it. I get that position. But you are already feeding from the devs that were exploited. Seems a bit hypocritical to use LLMs if you have that stance.

You have a nice website, and I noticed that it uses Tailwind too.

Did you buy Tailwind Plus to support them?

yes I have