3 ms·
That's a lot of churn. You should stop and ask yourself if it's worth being on the cutting edge all of the time. Are you making better projects as a result of d
by Touche 11y ago
That's a lot of churn. You should stop and ask yourself if it's worth being on the cutting edge all of the time. Are you making better projects as a result of dropping "old" tech the moment something shinier comes around?
Everything has tradeoffs. Elm has no server side rendering, for example.
- deleted 11y ago[deleted]
- wtetzner 11y agoIt may not be that he's trying to be cutting edge, so much as trying all of the options to see which one he wants to use.
- ricardobeat 11y agoConsidering rjs and prototype are way past dead and buried, that path covers a good 6-8 years, and up until React mirrors what most client-side devs have gone through.
- vdaniuk 11y ago>Are you making better projects as a result of dropping "old" tech the moment something shinier comes around? That's a lot of assumptions you are making there. Why "better projects" is the only metric considered here? Perhaps, OP utility in front end technologies is based on their learning. Or what's you reason to assume OP is dropping old tech "the moment something shinier comes around" and not after a reasonable period of exploration and trial? Prototype.js was created in 2005, 10 years ago. Angular was released in 2009. React was released in 2013. A lot of churn? Absolutely not. Someone staying current, perfecting their skills and knowledge? Good for them! The HN trend of "hipster shaming" people trying new, sometimes esoteric technologies (even if it's only for the novelty factor!) is not conductive to constructive discussions and really has no place in the community named Hacker News.
- rixed 11y agoUnless building a taste for long lived techs as opposed to favoring the newest reinvention of old ideas is part of the learning process?