As a primarly backend dev, I'm very comfortable with React and I don't particularly want to switch to Vue.js. React says me : learn the HTML basics and then deal with abstractions (proof: React Native !). Vue.js says me : deal with HTML templates, everytime, everywhere. Although we even end to deal with HTML in React, I think it's easier for a backend dev with no front experience at all to grasp it. I showed React to…
Why we chose Vue.js
71–80 of 282 posts
Re: Why we chose Vue.js
#72Vue.js is the most beginner friendly to write a complex web application.
Re: Why we chose Vue.js
#73I suppose Vue.js is not very TypeScript friendly?
Re: Why we chose Vue.js
#74Earlier quoted context omitted.
ng-cloak is your friend..
I guess but it feels like such an anti pattern. I have to tag every thing that uses the template system with ng-cloak and that assumes the angular css loads before the HTML which can still not be guaranteed it's just more likely. The worst part is many default values could be displayed but now we're hiding sometimes large junks when for the best UX you should show as much of the page as possible. Ultimately just not…
instead of
{{value}}
It is preferable to use ngBind instead of {{ expression }} if a template is momentarily displayed by the browser in its raw state before Angular compiles it. Since ngBind is an element attribute, it makes the bindings invisible to the user while the page is loading.
Re: Why we chose Vue.js
#75Earlier quoted context omitted.
Honest question, how do you know that it's the frontend that's slow and not the backend?
You only need to look at a DevTools timeline to see that it's the front-end which is slow: https://www.webpagetest.org/result/161021_08_XZF/ 600KB of CSS, 800KB of JS... That's fine on your MBP over WiFi but on most pages it locks up the main thread on my phone for a good 5-10 seconds.
Re: Why we chose Vue.js
#76I wish there were an equivalent to something like ember-fastboot for out-of-the-box server side rendering, though. (server-side rendering for those who care about progressive enhancement in the browser, not isomorphism).
Re: Why we chose Vue.js
#77Are any companies switching from React to Vue? I'd be interested in hearing about that.
We went with polymer for web standards, bigger ecosystem and great encapsulation options. Everybody loves the change.
Re: Why we chose Vue.js
#78After using React, I am firmly in the #nevertemplates camp. I don't ever want to learn a template DSL again when I could be using the full power of javascript.
Re: Why we chose Vue.js
#79Ok, so I've built stuff in Vue.js, React and Angular and I need to understand all the rage. I mean, Vue.js is just like Angular but with less features? I like that it's slimmer, don't get me wrong, but I just don't understand the "woah, Vue.js is the shit!" when we've had Angular for so long. I put this in contrast to React where it's a completely new concept.
Re: Why we chose Vue.js
#80After using React, I am firmly in the #nevertemplates camp. I don't ever want to learn a template DSL again when I could be using the full power of javascript.
Same here. In my opinion JSX is one of the best thing happened in the front-end world. Let's not forget how horrible Angular templating was: {{::item.name}}