Why We Chose Vue.js

at about.gitlab.com

8 up and 2 down, posted by xat 2743 days ago 8 comments

basically 2742 days ago. link 3 points ▲ ▼

Interesting article! I personally prefer the React way for serveral reasons. What hinders me to give vue a try is the seperation of HTML and JS. In Vue (it seems) you have to use a CSS selector to wire things together ("#journal" in the example).

Everyone should use what fits them best, but I don't want to ever again use Strings (here CSS selectors) to "bring things together". Maybe it's the Java background but something feels so very wrong about this to me (though there are also many examples of inappropriate String usage in Java, instead of using types).

Replies

MaxArt 2741 days ago. link 1 point ▲ ▼

You can pass a DOM element instead of a selector there. It's just like ReactDOM.render, only you can pass a selector too.

Plus you can pass a template property too so it won't use the element's content as a template.
Moreover, with Vue you can create .vue files that merge together the code, the template and the style of a single component. As a plus, you can use transpilers and compilers for all (Babel, Pug, Sass... you name it).

Finally you can even use JSX with Vue so you actually have maximum flexibility here.

xat 2742 days ago. link 1 point ▲ ▼

The nice thing about vuejs is, that you can also just define a render method and use JSX. So you don't have to use template strings.

https://vuejs.org/guide/render-function.html

basically 2742 days ago. link 3 points ▲ ▼

Thanks, now i need to take a closer look ;-)