4 ms·
This is true and in experience happens far quicker than 5 years for JS frameworks. Most of the frameworks I learned 5-10 years ago are already effectively dead
by ian0 4y ago
This is true and in experience happens far quicker than 5 years for JS frameworks. Most of the frameworks I learned 5-10 years ago are already effectively dead too.
But I think OPs main point stands, your far more likely to die by not shipping things early than by having to refactor occasionally. After 5 years 50% of businesses have failed [0] and this is far far higher for startups & side projects.
[0] https://www.bls.gov/bdm/entrepreneurship/entrepreneurship.htm https://www.bls.gov/bdm/entrepreneurship/entrepreneurship.ht...
- tabtab 4y ago> your far more likely to die by not shipping things early than by having to refactor occasionally. Know your org. A startup has very different priorities than a bank, for example. Small projects need different conventions than big projects, internal need diff than external, 200 user apps need diff than "web scale", etc. I'm more careful now to state the assumed environment because one size doesn't fit all. And fit your org, not your resume. Buzzword oriented programming is selfish; I've seen it make screwball messes.
- zdragnar 4y agoThe major JS frameworks have all been around for 5 years; several for 10 (react turns 10 this May). Compare that to the average tech employee tenure, or even the average lifetime of a startup company.
- dmitriid 4y agoI just pulled in a class-based component into a modern React project. It just worked with no adjustment. Now that's commitment to backward compatibility (and they can't have it any other way, they won't rewrite half of facebook just because their own framework changed).