3 ms·

The Vue 3 disaster (in my opinion) shook my trust in the framework forever. I immediately knew this is not a framework I will spend any more time in. What if I

The Vue 3 disaster (in my opinion) shook my trust in the framework forever. I immediately knew this is not a framework I will spend any more time in. What if I "upgrade" my apps to 3 and then Vue 4 comes along with yet another fundamentally different concept? This is not acceptable for apps with any kind of long time support requirement. Yes I know, Vue 2 paradigms are still usable in 3 but they feel very deprecated.

KaoruAoiShiho 4y ago
Don't think Vue 2 to Vue 3 is that bad, certainly nothing like AngularJS to Angular. You can still conservatively upgrade piecemeal elements of your stack and most of the code still just works.
gherkinnn 4y ago
Coming from Vue 0.x and 1, Vue 2 felt wrong. It didn’t know what it wanted. Classes and hooks and decorators and options and only some obscure combination offered acceptable TS support. Having only read the docs, Vue redeemed itself with version 3. There’s the options API we know and love from v1 and the new and intuitive composition API. The docs make it easy to decide and not to mix them up. And no useEffect fuckery.
runarberg 4y ago
I inherited a vue2 codebase with a vuex store, and upgrading to vue3 and pinia one component at a time over a course of 3-4 months was quite easy. The upgrade path is really clear and they did a good job making everything compatible so that it could be made gradually over a relatively long time.
- suction 4y ago
  3-4 months seems doable. We are usually asked to do it in a week or two.
  - runarberg 4y ago
    That seems like a bad idea from an engineer perspective. The migration path is designed to be gradual, that migrated and legacy code can live side by side in production. I honestly don’t know why anyone would enact a policy of migrating all at once when there is an alternative.
    - suction 4y ago
      The reason is superiors without an engineering background (but rather a "tech consultancy" background). Don't get me started.

KaoruAoiShiho 4y ago

Don't think Vue 2 to Vue 3 is that bad, certainly nothing like AngularJS to Angular. You can still conservatively upgrade piecemeal elements of your stack and most of the code still just works.

gherkinnn 4y ago

Coming from Vue 0.x and 1, Vue 2 felt wrong. It didn’t know what it wanted. Classes and hooks and decorators and options and only some obscure combination offered acceptable TS support. Having only read the docs, Vue redeemed itself with version 3. There’s the options API we know and love from v1 and the new and intuitive composition API. The docs make it easy to decide and not to mix them up. And no useEffect fuckery.

runarberg 4y ago

I inherited a vue2 codebase with a vuex store, and upgrading to vue3 and pinia one component at a time over a course of 3-4 months was quite easy. The upgrade path is really clear and they did a good job making everything compatible so that it could be made gradually over a relatively long time.

suction 4y ago
3-4 months seems doable. We are usually asked to do it in a week or two.
- runarberg 4y ago
  That seems like a bad idea from an engineer perspective. The migration path is designed to be gradual, that migrated and legacy code can live side by side in production. I honestly don’t know why anyone would enact a policy of migrating all at once when there is an alternative.
  - suction 4y ago
    The reason is superiors without an engineering background (but rather a "tech consultancy" background). Don't get me started.