4 ms·
I can relate. I wrote an essay on this a while back: https://www.nemil.com/musings/shinyandnew.html https://www.nemil.com/musings/shinyandnew.html Excerpt: Pi
by nemild 9y ago
I can relate. I wrote an essay on this a while back:
https://www.nemil.com/musings/shinyandnew.html https://www.nemil.com/musings/shinyandnew.html
Excerpt:
Pity the modern web or mobile app developer on Hacker News. As a full stack startup developer in 2012, you were building websites using Ruby/Rails on the backend, Backbone/Coffeescript/Underscore on the frontend, while deploying your app with Capistrano (or the relevant Python analog). By 2013, you'd transitioned to Node/Express/Mongo on the backend, Grunt/Ember on the frontend. In 2014, you'd switched whole hog over to the MEAN stack (now with promises), but experimented with Koa and considered a shift to Go (after the Express core contributor made the jump).
In 2015, you're using Gulp/ES2015/React on the front end, Express/Go on the backend, React Native over the native mobile languages, and slowly transitioning your system over to microservices with Docker. Soon, you'll be transitioning to Phoenix, figuring out if Angular 2 is the right choice - and maybe even plotting a world where Go can work on Android and where an open sourced Swift might fit into your stack. (I’m clearly exaggerating for effect, though this is a fair representation of what is popular in HN headlines)
- katzgrau 9y agoOne minor upside to the rapid change is that I can sit out an entire stack and hop back into relevancy with some totally new stack a year later.
- twhb 9y agoI'm not sure HN headlines - even ones like "we rewrote our codebase with X" - indicate that people are actually rotating libraries quickly. Rather, they indicate our quickly-shifting curiosity, and cherry-pick instances of people actually acting on it because they're interesting. Tellingly, the "rewrite" blog posts usually are coming not from the fad preceding the current, but something much older.