3 ms·
I experimented a little bit with Vue. I was a little bit disappointed about two points: 1. I couldn't CSS style a Vue component. I find components very importa
by _nalply 9y ago
I experimented a little bit with Vue. I was a little bit disappointed about two points:
1. I couldn't CSS style a Vue component. I find components very important and they should behave like HTML elements. It should be possible to write a <video> element in Vue if that element didn't exist.
2. I find the state management Vuex somewhat an afterthought. Some people say you will know when you need state management, but I think if the integration of state management is really seamless there is no need to avoid state management even for the most simple apps. So don't listen to these people and start with Vuex straight away, even if it takes a little bit more effort.
I'm sure that there are more points for an even better solution. However for the moment Vue seems to me the simplest, the most elegant and most intuitive framework. So I will use it for my future projects.
- yunyu 9y agoOne of the biggest selling points for single file components is styling (with optional scoping): https://vue-loader.vuejs.org/en/features/scoped-css.html https://vue-loader.vuejs.org/en/features/scoped-css.html If you need to override child component styles from a parent (bad idea in 99.999% of cases), /deep/ would work.
- _nalply 9y agoVue components are second class citizens compared to HTML elements, because you don't style them, you pass them props. This idea with stylable components is for a different framework, perhaps.
- jaequery 9y agowhat? vue does all that. i don't think the op tried vue at all, lol.