That’s pure gold to feed my coding agents and let them decide which model/service/framework use for each specific task. Thanks for sharing Addy! Great job compiling all these valuable resources in one single post.
Thanks Cesar! That's exactly the kind of use case I was hoping this would enable - letting the agents themselves navigate the decision tree of which tools and frameworks to use for each specific context.
For the agentic future specifically, Replit's architecture seems well-positioned since AI agents can work directly with the underlying system while users can choose their preferred interface layer on top.
I believe one of the reasons for CLI re-emergence is long-term web fatigue. We all know how fantastic web is, but it could use some ozempic. That frustration that even though I've over 5000 times more RAM in my current MacBook compared to my first computer - latency is worse than in old good terminal.
Prophecies about moving business logic to agents seemed reasonable, and now we're officially in the first example of new era.
Great point about web fatigue driving the CLI comeback! The irony is kinda striking - we have thousands of times more computing power yet somehow terminal interactions feel more responsive than web apps. It makes perfect sense that AI agents would start there first, where there's direct feedback without all the overhead.
Thanks Addy! I remember the amazing event we both attended - EdgeConf 2015 in London’s Facebook office. On the bleeding edge of promoting service workers and performance.
I feel like that was the last notable movement, ending in putting Lighthouse as a primary tenant in Chrome DevTools for the web anti-bloat. Long gone. Median Page Weight (almanac.httparchive 2022) - 1440KB of which 461KB is JS!
Solid reset of how we build “online software” is just around a corner!
EdgeConf 2015! What a throwback - that was such an amazing event. We're actually doing some analysis around the performance of vibe-coded and AI-generated apps right now to understand how much more work there is to do there.
The 'solid reset' resonates - maybe AI agents demanding efficient, direct interfaces will be the forcing function the web never had. Sometimes it takes a completely different paradigm to make us question what we've been accepting as normal.
Thank you for amazing articles. They are always on point, positive, but also indicating the problems that AI introduce. A lot of AI posts are just hype and a bubble of “AI is better than us and will replace us”. Now when I use AI more and more (from Copilot to Cursor), I start seeing not only where it does a good job, but also where it falls apart. And for some reason a lot of people ignore the last part
That’s pure gold to feed my coding agents and let them decide which model/service/framework use for each specific task. Thanks for sharing Addy! Great job compiling all these valuable resources in one single post.
Thanks Cesar! That's exactly the kind of use case I was hoping this would enable - letting the agents themselves navigate the decision tree of which tools and frameworks to use for each specific context.
I am getting specialist on this field and looking for new job opportunities in this area. Which job post resources would you recommend to look for?
Where does replit fall on the spectrum?
For the agentic future specifically, Replit's architecture seems well-positioned since AI agents can work directly with the underlying system while users can choose their preferred interface layer on top.
I believe one of the reasons for CLI re-emergence is long-term web fatigue. We all know how fantastic web is, but it could use some ozempic. That frustration that even though I've over 5000 times more RAM in my current MacBook compared to my first computer - latency is worse than in old good terminal.
Prophecies about moving business logic to agents seemed reasonable, and now we're officially in the first example of new era.
Terminal is always the first.
Exciting what's next!
Great point about web fatigue driving the CLI comeback! The irony is kinda striking - we have thousands of times more computing power yet somehow terminal interactions feel more responsive than web apps. It makes perfect sense that AI agents would start there first, where there's direct feedback without all the overhead.
Thanks Addy! I remember the amazing event we both attended - EdgeConf 2015 in London’s Facebook office. On the bleeding edge of promoting service workers and performance.
I feel like that was the last notable movement, ending in putting Lighthouse as a primary tenant in Chrome DevTools for the web anti-bloat. Long gone. Median Page Weight (almanac.httparchive 2022) - 1440KB of which 461KB is JS!
Solid reset of how we build “online software” is just around a corner!
EdgeConf 2015! What a throwback - that was such an amazing event. We're actually doing some analysis around the performance of vibe-coded and AI-generated apps right now to understand how much more work there is to do there.
The 'solid reset' resonates - maybe AI agents demanding efficient, direct interfaces will be the forcing function the web never had. Sometimes it takes a completely different paradigm to make us question what we've been accepting as normal.
Thank you for amazing articles. They are always on point, positive, but also indicating the problems that AI introduce. A lot of AI posts are just hype and a bubble of “AI is better than us and will replace us”. Now when I use AI more and more (from Copilot to Cursor), I start seeing not only where it does a good job, but also where it falls apart. And for some reason a lot of people ignore the last part
This is now one of my favorite blogs - thanks