But some of us do work on front-end applications where even modern frameworks are scrutinized. I've started to dream of a maintainable application with no runtime on top of the browser itself (no vDOM)
IMO frameworks nowadays don't give you much more than a rope to hang yourself with, it's up to developers to recognize this. But some applications do need these patterns in order to build front-end applications with dozens of developers on the same team. The unfortunate reality is that too many people think they need use the same tech for a landing page; and too few people with front-end skills seem capable of profiling (in Chrome! nevermind trying to figure out where your GC pressure is coming from in IE11)
But this article is pretty boring. I can think of some concerns that the applications I work on need solved:
* Maintainable (TypeScript helps a ton with this)
* Stylizable/Themable (emotion/JSS, etc.; pick your poison)
* Reusable (presentational components in React; I imagine Vue could work for us as well)
* Asynchronous, reacting to events from user input/websocket/timers/local+remote storage appropriately
I am currently looking into it :) So far the theming does not appear to be fleshed out; I'm about to compare some performance metrics with some of our animated components. I'm also not sure what the state management solution looks like, but I only spent a couple of hours setting up today
Comments
But some of us do work on front-end applications where even modern frameworks are scrutinized. I've started to dream of a maintainable application with no runtime on top of the browser itself (no vDOM)
IMO frameworks nowadays don't give you much more than a rope to hang yourself with, it's up to developers to recognize this. But some applications do need these patterns in order to build front-end applications with dozens of developers on the same team. The unfortunate reality is that too many people think they need use the same tech for a landing page; and too few people with front-end skills seem capable of profiling (in Chrome! nevermind trying to figure out where your GC pressure is coming from in IE11)
But this article is pretty boring. I can think of some concerns that the applications I work on need solved:
* Maintainable (TypeScript helps a ton with this)
* Stylizable/Themable (emotion/JSS, etc.; pick your poison)
* Reusable (presentational components in React; I imagine Vue could work for us as well)
* Asynchronous, reacting to events from user input/websocket/timers/local+remote storage appropriately
* Accessible via keyboard
I believe the answer is Svelte.
I am currently looking into it :) So far the theming does not appear to be fleshed out; I'm about to compare some performance metrics with some of our animated components. I'm also not sure what the state management solution looks like, but I only spent a couple of hours setting up today