A few months ago, whilst deep in a dark cloud of personal overwhelm caused by the unrelenting exponential growth of the web ecosystem, I wrote abou...
For further actions, you may consider blocking this person and/or reporting abuse
No matter how many JS framework are out there, the market will ever choose the technology with lowest cost, easy development and with more developers working with. So, why not improve the technology that we already have?. In my opinion, not only from the web dev point, there could be hundreds of framework, 3 or 4 will ever be the mainly used, and, make framework just for fun and for understand some concepts.
An absolutely valid point!
Some people may argue that the technology we already have can be tricky to navigate. There is likely years of tech debt wrapped up in React, for example. You know how sometimes a feature gets so convoluted in production, with fix on top of fix, that sometimes it's better to rip it out and start again rather than embark upon a gruelling refactor?
I'm speculating here, but fixing what already exists may limit innovation. Then again, working within constraints is also something that can spark innovation.
There will always be pros and cons to any approach. Always two sides to the story. Always more than one approach — and each one as valid as the next.
Yeah, you're right, at this point, I think that JS frameworks has become in a matter of subjectivity, maybe due to the nature of JS? 🤔, because, I've not seen other language with this situation (hundreds of frameworks). JavaScript ecosystem is a case study, something should make a thesis about this. :D
How much does a ticket cost?
I hear my senior talking:
Works everywhere 😃
Good post!
Thanks, Salma for sharing your experience with the dev community.
nice ...
While that sounds all good. In reality it's not all sunshine and rainbows.
The "platform" does not support all the features that JS frameworks provide such as SSR, partial hydration etc.
The "platform" moves at a snail pace compared to the OSS JS fws that innovate so much more quickly to offer better DX, performance and features.
Using the "platform" is so cumbersome, that the vast majority of the time you need to use other frameworks to even compose WCs and handle state etc...
Further, frameworks makes sure that your code can run on not so old browsers, like shadow Dom is relatively new and you probably have to add polyfills, and another example is import maps, and they're still under consideration+ not supported by every browser...
Vanilla! Vanilla! Vanilla! Frameworks And Libraries are mere details. I only use them as plugins. That's what Uncle Bob taught me.
I launch the #noRAV # tag : no React no Angular, no Vue :-)
What should we use? XD
All depend of your constraints.
For my personal projects I have gathered some functions I found useful in a little library.
Among those functions :
Create your own :-)
Here is an example MVU Sample
Libraries > Frameworks