It's only when people think of Typescript as a new language where everything must have types things start to go wrong — Javascript won't ever be that. There'll always be a tiny but super useful library from 2004 which has its jQuery dependency removed just 6 months ago, and won't ever get Typescript support, and you have to use it — and if you're a purist that's going to spoil your lunch.
Don't be a purist — a project using Typescript at 50% of its codebase is vastly better than one that uses it at 0%, even if all its asserts are :any's.
I currently love Vue.js as it is. I have followed along with the fixes, improvements, and changes, and continue to think the same thing... "Am i just lucky that I never run into ANY of these problems? Am I using the framework wrong because I am NOT running into these issues?"
Like you, i mainly use single-file components. But to me, that is the best way to use Vue in an advanced project. So I have been wondering the same thing during this whole launch, "does anyone actually care about these changes or are we starting to make this beautiful framework into something that is unnecessarily complicated?"
If you're talking about changing from the current v2 object syntax to v3 composition api might be hard indeed, then I agree with you... but I'm hoping we'll get some compatibility layer soon enough.
EDIT: According to Evan we'll get a "compat build" in the RC phase [1]
[1] https://medium.com/the-vue-point/plans-for-the-next-iteratio...
I don’t get it. Seriously, Vue 2 is great, so much fire and forget. There’s a bunch of problems that I am supposed to have, which justifies these changes, but I really don’t have them. Single file components solve it all for me.
This feels like Vue is trying to become React, but ... I’m using Vue because I think it’s much more valuable than React. I also get that it’s said that none of the things I like will change and I could just keep using it as is, but when was that ever really true - the new features always take more of the mindshare than keeping existing users.
This might be the curse of us all: the people who build successful things tend to be the most extreme users of their own thing. It helps you by making you have high standards at the beginning, but later on, if you keep serving yourself, you’ll end up with something like Angular where it eclipses past the sweet spot where most of the users are and goes for ever more advanced things with not so much of an audience, just because you’ve been solving your own problem and that has even a good metric thus far.