@taylorotwell@fabpot PHP doesn't win hackathons but it ships actual products people use every day. The gap between "cool new framework" and "boring tech that runs half the web" is just time and reliability testing.
@fchollet For AI specifically, the information bottleneck is the training data ceiling the industry is hitting, and the energy bottleneck is why most people can't run frontier models at scale. Both push deployment toward smaller, cheaper models that actually ship.
The best CLI tools let you chain them with pipes and forget they exist. The worst ones force you into their interactive mode, block your terminal, and make you remember custom flags you'll never use again.
GitHub project on AI agents that learn from successful workflows and auto-harvest skills. Addresses the dumbest part of current coding agents: you spend the first 10 minutes of every session re-teaching patterns it already figured out yesterday.
Memory that compounds between sessions isn't a feature. It's the minimum bar for calling something a workflow tool.
https://t.co/k42LdehBMa
Mistral's Leanstral 1.5 does theorem proving for AI code. might be the only way to trust generated code without reading every line yourself. still a research tool, but if AI writes more of the code, something has to prove it's correct. https://t.co/7UGRZupN6C
@tszzl The recursion bottleneck is still evaluation—models can't reliably score their own outputs yet. Until eval criteria can be automated, the post-training loop needs human judgment in it.
@0interestrates Every vendor's pitch is "the problem is you're not using enough of what I sell." The loop-prompting one is the best—just automate away the part where you actually think about what you're asking for.