4 ms·
That’s an interesting idea, essentially to get the usefulness of Vue single file components but without involving a build process. I would expect development a
by burlesona 7y ago
That’s an interesting idea, essentially to get the usefulness of Vue single file components but without involving a build process.
I would expect development and debugging could be somewhat easier since you’ve just got annotated HTML (no build pipeline), but I would also expect that runtime performance would be worse (or at least it would be harder to write an implementation as performant).
I could see this being a very nice option for simple sites, where you just have a bit of interesting UI on the page (menus, forms) and want to write it declaratively, but going to a full-on SPA framework is overkill.
VueJs fit that description really well at version 1. I love Vue, but I feel it has moved much in the direction of a full all or nothing framework these days, especially with the mental hoops they’ve gone through in v3 (setup + hooks) to take the paradigm and make it typescript friendly.
- yurishimo 7y agoI like that Vue 3 is sticking to their API though even with the new stuff. React hooks felt like we were doing something wrong while Vue just feels like a natural progressive enhancement. It’s also cool that you can use the normal Vue lifecycle stuff with the composition api. Episode 129 of full stack radio podcast has a lot of good info in it!
- mahesh_rm 7y agoI use Vue (2) in this way, and Angular when I need a full fledged SPA (heavy) environment.