3 ms·

Did you read the article? Here's a snippet from the beginning: > Do front end technologies actually change that quickly? > In the sense of major view technolo

Raphmedia 8y ago
I never understood this argument. You are comparing frameworks. All of those are nothing but fancy ways to play with the DOM. There's nobody telling anyone to jump from one to the other. Do you migrate your PHP or .NET projects every time a new framework comes out? No. You shouldn't with front-end either. It's as if you printed a table that goes "CakePHP; Yii; CodeIgniter; Laravel; Symfony; Phalcon; Zend." and then complained about the PHP ecosystem.
- filleduchaos 8y ago
  Did you actually read the argument though?
bzalasky 8y ago
Small correction on the chart, React has actually been open sourced for ~5 years, React Native is ~3 years old. As far as how fast frontend technologies are changing, in my ~10 year career, I've only had to use jQuery (~2008-present), Backbone (~2012-present) and React (2015-present) professionally. These libraries weren't swapped out on a whim, and I still use all 3 in different projects on a weekly basis. While I've dabbled with most of the others, I haven't selected them or encountered them professionally. To some extent, I think library churn can be attributed to keeping things interesting when the problems you're solving are less interesting. Most frontend engineers could probably benefit from rolling their own SPA library (not for production use, but to learn how the different pieces come together). There's probably room for a few more "From Scratch" tutorials in this space akin to Destroy All Software's series of screencasts. Working through something like this would make it clear that the differences between the libraries above are smaller than it might otherwise seem.

Raphmedia 8y ago

I never understood this argument. You are comparing frameworks. All of those are nothing but fancy ways to play with the DOM. There's nobody telling anyone to jump from one to the other. Do you migrate your PHP or .NET projects every time a new framework comes out? No. You shouldn't with front-end either. It's as if you printed a table that goes "CakePHP; Yii; CodeIgniter; Laravel; Symfony; Phalcon; Zend." and then complained about the PHP ecosystem.

filleduchaos 8y ago
Did you actually read the argument though?

bzalasky 8y ago

Small correction on the chart, React has actually been open sourced for ~5 years, React Native is ~3 years old. As far as how fast frontend technologies are changing, in my ~10 year career, I've only had to use jQuery (~2008-present), Backbone (~2012-present) and React (2015-present) professionally. These libraries weren't swapped out on a whim, and I still use all 3 in different projects on a weekly basis. While I've dabbled with most of the others, I haven't selected them or encountered them professionally. To some extent, I think library churn can be attributed to keeping things interesting when the problems you're solving are less interesting. Most frontend engineers could probably benefit from rolling their own SPA library (not for production use, but to learn how the different pieces come together). There's probably room for a few more "From Scratch" tutorials in this space akin to Destroy All Software's series of screencasts. Working through something like this would make it clear that the differences between the libraries above are smaller than it might otherwise seem.