4 ms·

We've been pretty happy with Vue 2.6 and haven't had the motivation to take the leap. I did try it and even though it's advertised as somewhat backward compati

We've been pretty happy with Vue 2.6 and haven't had the motivation to take the leap. I did try it and even though it's advertised as somewhat backward compatible it did break lots of things, which was totally expected and it's a major release. Also we couldn't figure out a lot of things, like how can I access the $children like before, why does everything show Object proxy in console, etc. Posting on SO and forums also didn't yeild much help since everyone is still discovering it too I guess. So in the end we decided why fix something which ain't broken for now. Vue 2 still kicks ass performance wise and is really easy to use.

lwansbrough 5y ago
There's a migration build available which will allow you to migrate more gracefully, should you choose to change your mind. (It runs the Vue 3 runtime with Vue 2.6 + 3 APIs.)
that_guy_iain 5y ago
I was looking into using v3 it seems like most libraries only work for v2
pjmlp 5y ago
When I am just yet another dev in the team, I use whatever the FE team decided upon, however on my own projects I use Web Components with lithtml. The browser underlying stack is always going to be there regardless of what is fashionable to wrap around it.
- cmwelsh 5y ago
  That’s not necessarily a belief that holds true universally. Plenty of developers have found that React and JSX are two technologies that have beautifully matured outside of their initial home in the web browser ecosystem. To use your phrasing, React and JSX are always going to be there regardless of what is fashionable for them to be wrapped around.
  - pjmlp 5y ago
    If you mean React Native, many of those devs are now adopting Flutter fashion, at least from the iOS and Android corners of the Internet I happen to move around. Cordova => React Native => Flutter => who knows
    - cmwelsh 5y ago
      Flutter looks very exciting, iff your team is willing to switch away from JavaScript. I’ve always been excited about Dart as a better JavaScript.
MentallyRetired 5y ago
I personally love Vue 2.6. I'm not a huge fan of the composable API.
- MatekCopatek 5y ago
  In case you're not aware - the Composition API is entirely optional and will most likely remain that way. It brings more flexibility but also adds complexity and makes components less readable.
conradfr 5y ago
Did you try to migrate with Vue 3.1 and it's compatibility layer? It helped me a lot.
deergomoo 5y ago
There is gonna be a Vue 2.7 that backports a lot of 3 functionality (particularly the Composition API, which is available in 2.x as a plugin currently but with caveats), so I don't think there's any pressure to upgrade even from the Vue team themselves. I believe `npm install vue` even still gives you Vue 2.

lwansbrough 5y ago

There's a migration build available which will allow you to migrate more gracefully, should you choose to change your mind. (It runs the Vue 3 runtime with Vue 2.6 + 3 APIs.)

that_guy_iain 5y ago

I was looking into using v3 it seems like most libraries only work for v2

pjmlp 5y ago

When I am just yet another dev in the team, I use whatever the FE team decided upon, however on my own projects I use Web Components with lithtml. The browser underlying stack is always going to be there regardless of what is fashionable to wrap around it.

cmwelsh 5y ago
That’s not necessarily a belief that holds true universally. Plenty of developers have found that React and JSX are two technologies that have beautifully matured outside of their initial home in the web browser ecosystem. To use your phrasing, React and JSX are always going to be there regardless of what is fashionable for them to be wrapped around.
- pjmlp 5y ago
  If you mean React Native, many of those devs are now adopting Flutter fashion, at least from the iOS and Android corners of the Internet I happen to move around. Cordova => React Native => Flutter => who knows
  - cmwelsh 5y ago
    Flutter looks very exciting, iff your team is willing to switch away from JavaScript. I’ve always been excited about Dart as a better JavaScript.

MentallyRetired 5y ago

I personally love Vue 2.6. I'm not a huge fan of the composable API.

MatekCopatek 5y ago
In case you're not aware - the Composition API is entirely optional and will most likely remain that way. It brings more flexibility but also adds complexity and makes components less readable.

conradfr 5y ago

Did you try to migrate with Vue 3.1 and it's compatibility layer? It helped me a lot.

deergomoo 5y ago

There is gonna be a Vue 2.7 that backports a lot of 3 functionality (particularly the Composition API, which is available in 2.x as a plugin currently but with caveats), so I don't think there's any pressure to upgrade even from the Vue team themselves. I believe `npm install vue` even still gives you Vue 2.