We are really considering dropping Vue 2 and going Vue 3 only, as the misalignments between them became harder to smooth out. Any objections or ideas? - ThreadSky

vueuse.org • 101 days ago

We are really considering dropping Vue 2 and going Vue 3 only, as the misalignments between them became harder to smooth out.

Any objections or ideas?

Comments

ashokgelal.bsky.social•100 days ago

None from my side

djodi.bsky.social•100 days ago

No objection, Vue 3 only!

anderswikstrom.se•100 days ago

Go for it. It’s easy enough to pin to an older version for legacy projects.

cgvweb.com•100 days ago

Makes sense. I don’t see why maintaining support for an EOL product is worth it long term. If embracing Vue 3 fully allows it to improve the utilities and grow further, I’m all for it.

If the Vue 2 community needs it, they can pin the version or even fork their own.

warmwestwind.bsky.social•100 days ago

well, if the Python community is any indication,

peterg69.bsky.social•100 days ago

Go for it!

chrisviolette.dev•100 days ago

danielwaltz.me•100 days ago

Yeah... I also think it's time. I still have a couple older Vue 2 apps at work, but it's trivial to version lock. Exciting!

d3-max-t.bsky.social•100 days ago

Definitely yes. Do a new major for Vue3 only and clean it up. 👍 🍻

gbw.dev•100 days ago

Yes! Please do

nestor.rip•100 days ago

stefanobartoletti.it•101 days ago

Maintaining two different codebases seems like a big effort, possibly becoming increasingly unnecessary.
It it was a project of mine, I would concentrate on the latest and newest version, with a grace period to let users migrate.

sinneida.bsky.social•100 days ago

Since 2.7 is EOL, I think it's a good idea 😁

kye.boats•99 days ago

Anyone still carrying around Vue 2 surely can’t be keeping everything else up-to-date.

fuzzyma.bsky.social•100 days ago

If someone really want the new goodies, they can either copy your code and adapt or _finally_ make the switch to Vue 3.

Make your devs happy; Upgrade to Vue 3 :D

vueuse.org•100 days ago

https://github.com/vueuse/vueuse/pull/4349

bensheedy.com•100 days ago

h.guliyev.com•100 days ago

Vueuse supporting both 2 & 3 in the beginning was really good to allow everyone to upgrade in a timely fashion. There was enough time for this so far. Supporting vue 2 further will be preventing the remaining ones from switching and thus stopping progress. So it is for everyone's benefit to drop v2

applelo.bsky.social•100 days ago

Do it 😈

scottbedard.net•100 days ago

With 2.x being EOL, I think it’s appropriate for that to happen. It’s unfortunate, but at some point users must accept they are using legacy software, and understand that the rest of the ecosystem must move on.

thealexlichter.com•101 days ago

Would align with whatever @esm.dev does with regard to Pinia!

antfu.me•101 days ago

@esm.dev drop Vue 2, when? 🥹

esm.dev•100 days ago

I was thinking of still supporting vue 2.7 until it becomes a problem

esm.dev•100 days ago

Is this the death of vue-demi? 🥺

antfu.me•100 days ago

Um, I am thinking that yes.

Now in Vue 3, Ref now accepts two generics where Vue 2 only accepts 1. There are types like ShallowRef, MaybeRef, MaybeRefOrGetter, etc, are not in Vue 2. For types I don't really know how to align them perfectly 😇

esm.dev•100 days ago

That’s true
I think I might upgrade Pinia to 2.7 in v2 and release Pinia 3 with only support for Vue 3 next year

filrakow.ski•101 days ago

I allow it

swirlingskirts.bsky.social•100 days ago

Sounds fine to me

epicquotes.bsky.social•100 days ago

If I have ever made any valuable discoveries, it has been due more to patient attention, than to any other talent
- Isaac Newton
Join for more: http://epic-quotes.org

blackcodemath.bsky.social•100 days ago

Just here to show some love to Vue. I'm actually about to dive back into an old Vue 3 project and connect it with this cool new ATProto thing. Today! BTW, can you do a Vue Starter Pack? Or point to an existing one?