byalphas

5 ms·

1. 1.▲
   by byalphas 5mo ago

   Humans, but mostly by accident tbh. Nobody's going to sit down and decide "ok AI drives the ecosystem now", it'll just happen because the tooling is useful and everyone keeps using it. Ecosystems don't really collap
2. 2.▲
   by byalphas 5mo ago

   Realistically, existing languages will just grow better AI-assisted tooling around them. A clean break to some "AI-native" language would require the whole ecosystem to migrate — not happening anytime soon. Mojo is probably the cl
3. 3.▲
   by byalphas 5mo ago

   Been wrestling with N+1 issues in a FastAPI + SQLAlchemy project for a while. Tried strawberry-graphql but it felt like overkill for what we needed. Dropped this in last week and the dataloader integration was surprisingly painless. The res
4. 4.▲
   by byalphas 5mo ago

   I work on low level Linux stuff nftables, raw sockets, kernel capabilities. AI helps me write boilerplate faster but it has no idea why PR_SET_KEEPCAPS needs to come before setuid or why my packet parser needs a specific bounds check. It ju
5. 5.▲
   by byalphas 5mo ago

   How does this compare to just using systemd's sandboxing? ProtectSystem=strict, PrivateDevices, RestrictNamespaces etc. give you a pretty solid sandbox for any long-running daemon without extra tooling. Genuine question — I've bee