4 ms·

I’m using Vue as a UI for a desktop app for developer collaboration (https://aether.app https://aether.app), whose Vue part is about 60,000-70,000 lines of code

I’m using Vue as a UI for a desktop app for developer collaboration (https://aether.app https://aether.app), whose Vue part is about 60,000-70,000 lines of code. I guess this makes me a large, advanced user. 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.

alex_marchant 7y ago
I hear you, we use this at work and this rings true to our experience as well. One thing though is recently we've started experimenting with typescript? Have you used that? I find that you have to jump through hoops to get typescript and Vue to work together. Looking forward to a form of Vue with better support there.
- rolleiflex 7y ago
  Yes, I'm using Typescript with Vue. As long as you accept that Typescript is an addition to JS, that is, most of the things you work on will not have Typescript on their own, you can 'gate' it to your parts (i.e. enforce and assert types on your boundaries) and have no problems with it. 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.
  - alex_marchant 7y ago
    Vue is the backbone of our apps, not a small jquery library, good prop types and such is key to day to day work IMO.
- furicane 7y ago
  I've been using vue, nuxt and typescript without any issues so far (6 months with TS though). It's not vue that's at fault for troubles with TS.
ru999gol 7y ago
I'm curious, I'm maintaining a similarly sized React app. What are the benefits of Vue (2) over React?
- earthboundkid 7y ago
  It has a sane model for dealing with reactivity and doesn't insist on always using immediate mode. React runs into all these weird issues like stale closures because everything is always rendered every time. Vue just makes it all much simpler to grok because the setup function is only run once.
jacurtis 7y ago
I couldn't agree more! I too use Vue.js 2 as what i would call an advanced user. I use it daily as my primary front-end framework. 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?"
- mahesh_rm 7y ago
  I can't understand how this cycle of unnecessary complexity addition repeats over and over again. Indeed I find Vue 2 perfect as it is, and cannot see the motivation beyond these changes.
ratww 7y ago
What changes are you talking about? Are you aware that Single File Components won't be removed? Asking because a lot of people on Twitter and Reddit seem to be under this impression that it's going away... 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-iteration-of-vue-js-777ffea6fabf#086b https://medium.com/the-vue-point/plans-for-the-next-iteratio...
- ehutch79 7y ago
  v2 object syntax is supoosed to be staying
earthboundkid 7y ago
I disagree. Making renderless components in Vue 2 is sort of a pain. It can be done, but it doesn't feel natural. I'll be happy to have it simplified. And if you don't want to use it, the options API will still be around.

alex_marchant 7y ago

I hear you, we use this at work and this rings true to our experience as well. One thing though is recently we've started experimenting with typescript? Have you used that? I find that you have to jump through hoops to get typescript and Vue to work together. Looking forward to a form of Vue with better support there.

rolleiflex 7y ago
Yes, I'm using Typescript with Vue. As long as you accept that Typescript is an addition to JS, that is, most of the things you work on will not have Typescript on their own, you can 'gate' it to your parts (i.e. enforce and assert types on your boundaries) and have no problems with it. 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.
- alex_marchant 7y ago
  Vue is the backbone of our apps, not a small jquery library, good prop types and such is key to day to day work IMO.
furicane 7y ago
I've been using vue, nuxt and typescript without any issues so far (6 months with TS though). It's not vue that's at fault for troubles with TS.

ru999gol 7y ago

I'm curious, I'm maintaining a similarly sized React app. What are the benefits of Vue (2) over React?

earthboundkid 7y ago
It has a sane model for dealing with reactivity and doesn't insist on always using immediate mode. React runs into all these weird issues like stale closures because everything is always rendered every time. Vue just makes it all much simpler to grok because the setup function is only run once.

jacurtis 7y ago

I couldn't agree more! I too use Vue.js 2 as what i would call an advanced user. I use it daily as my primary front-end framework. 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?"

mahesh_rm 7y ago
I can't understand how this cycle of unnecessary complexity addition repeats over and over again. Indeed I find Vue 2 perfect as it is, and cannot see the motivation beyond these changes.

ratww 7y ago

What changes are you talking about? Are you aware that Single File Components won't be removed? Asking because a lot of people on Twitter and Reddit seem to be under this impression that it's going away... 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-iteration-of-vue-js-777ffea6fabf#086b https://medium.com/the-vue-point/plans-for-the-next-iteratio...

ehutch79 7y ago
v2 object syntax is supoosed to be staying

earthboundkid 7y ago

I disagree. Making renderless components in Vue 2 is sort of a pain. It can be done, but it doesn't feel natural. I'll be happy to have it simplified. And if you don't want to use it, the options API will still be around.