Around 2014, this article triggered the rise of React in Japan.
Why the concept of virtual DOM shakes our soul-Qiita
In this article, the reason why Virtual DOM is required is that "design and speed are compatible", but I think that there were few cases where the front end of the Web was compatible with design and speed at that time.
Nowadays, the rise of frameworks such as React and Vue makes it much easier to satisfy this "design and speed", but in addition to this, " good development experience " is now required. I feel like I am.
In fact, I now often use frameworks such as Nuxt.js and develop with the backend and frontend loosely coupled. After experiencing the goodness of this development experience, I wonder if it will not be possible to return to the development with the general backend and frontend tightly coupled.
So, in the future, the front-end framework will be
- design
- speed
- Development experience
I think that it will continue to be popular and obsolete, centering on these three.
It's an extreme theory that I have decided on my own, so please subtract it.
For me, Angular and Vue.js are Java applets, Flex apps, and Silverlight apps. It's not that it hasn't evolved at all, but I feel that what I want to do with it hasn't changed much. A stateful application that runs on the stateless web and can be launched from the web without installation. Yes, a tool for running desktop apps that have been created in the same way since Win95 in the browser sandbox. So what's the big difference from before? Now you don't have to choose a platform that works for you! I realize that.
Good and easy to use. Things that can be developed quickly.
0 コメント:
コメントを投稿