4 ms·
10 years ago it was Heroku and Three.js.
by gbgarbeb 6mo ago
10 years ago it was Heroku and Three.js.
- boringg 6mo agoNew one coming in 5 years. Cycle repeats itself.
- guelo 6mo agoI don't think so, AIs are going to freeze the tooling to what we have today since that's what's in the training corpus, and it's self reinforcing.
- telotortium 6mo agoNah, the good LLMs can generally web search and read documentation well enough that the fact that pre-training isn’t up to the minute is not a serious concern. Badly-documented projects are more of a concern, but they weren’t likely to get much pre-AI usage either.
- seattle_spring 6mo ago10 years ago it was Heroku and Ruby on Rails*
- dzonga 6mo agobut now Ruby on Rails is not a circus like how Next.js is. see [0]: Rails security Audit Report [0]: https://ostif.org/ruby-on-rails-audit-complete/ https://ostif.org/ruby-on-rails-audit-complete/
- seattle_spring 6mo agoCan you elaborate as to why your linked article would suggest nextjs to be a "circus"? If anything, DHH (founder of RoR) and his Looney-Tunes opinions are much closer to a circus sideshow than anything I've seen come out of Vercel.
- bdcravens 6mo agoMore like 15. By 2016, Rails was supposedly dead and we were all going to be running the same code on the front end and back end in a full stack, MongoDB euphoria.