How and why we moved to Vue.js

Re:How and why we moved to Vue.js by hashkb on Sunday February 11, 2018 @11:48AM (#16353387)

Generally speaking a regular dev under normal time/budget constraints will.het better performance out of React or Vue. It takes more time and more expertise to get that "optimal" VanillaJS performance. Analogy: Ruby vs C.

[ Parent | on HN ]

Re:How and why we moved to Vue.js by the_duke on Sunday February 11, 2018 @12:30PM (#16353608)

I disagree.

With React, you can quite quickly stumble over performance bottlenecks in non-trivial app when you don't know what you are doing.

Especially on mobile devices.

[ Parent | on HN ]

Re:How and why we moved to Vue.js by mercer on Sunday February 11, 2018 @01:08PM (#16353842)

Could you give some examples? When it comes to trivial apps I'd say jQuery could be fine, but it feels like kind of working against what it was designed for. But for non-trivial apps I can think of at least as many jQuery 'gotchas' as I am aware of in React.

[ Parent | on HN ]

Re:How and why we moved to Vue.js by Can_Not on Friday February 16, 2018 @10:17AM (#16392881)

If your app is non-trivial, I expect maintainability nightmares in vanilla long before performance issues (which will be in both for people who don't know what they are doing).

[ Parent | on HN ]