6 ms·

Interested in the steady drop in satisfaction with Vue since 2018. I remember being positively impressed when I looked into it. Is it simply due to more usage

Interested in the steady drop in satisfaction with Vue since 2018. I remember being positively impressed when I looked into it. Is it simply due to more usage in actual systems causing people to dislike tools they really work with, or is the framework developing in a direction people are unhappy with?

sgdesign 5y ago
I think every framework sees this kind of drop once it gets widely adopted. Probably a combination of being confronted with real-world use cases, as well as the appeal of newer solutions that promise to do the same thing even better.
killingtime74 5y ago
It’s just the hype cycle. It’s only improved in recent years
nawgz 5y ago
Vue.js is heavily magic and doesn't support basic React concepts like render props. How is that possibly a popular framework? Like any "easy" library, you'll run into hard situations with no solutions.
- searchableguy 5y ago
  What do you mean? Vue has slots which is similar to render props. https://vuejs.org/guide/components/slots.html#scoped-slots https://vuejs.org/guide/components/slots.html#scoped-slots
  - nawgz 5y ago
    After a read, I guess it does. A developer I respected claimed it was not easy to pass components down like this. Now I no longer respect him. Also, I still don't respect vue. Look at this abomination <MyComponent v-slot="{ text, count }"> {{ text }} {{ count }} </MyComponent>
    - pcthrowaway 5y ago
      You can respect that developers you respect are humans who make mistakes and misunderstand things. As you've done, you've made an inaccurate claim and learned from it. Hopefully you still respect yourself. Also (and I'm not familiar with Vue to know if this is the case), the state of software is such that you can make a claim and have it invalidated a few days later after an update comes out.
      - nawgz 5y ago
        > You can respect that developers you respect are humans who make mistakes and misunderstand things No I can't. Seriously, it was a joke, he's my best friend, but I guess I misunderstood his claim or he misunderstood render props! From what I can see reviewing Vue's 2.x docs, they seem to have had this "slots" idea for a while. I get a little bit ill from looking at that syntax though so I think I'll refrain from arguing about the library again!
- AlfeG 5y ago
  I understand all this traction with Composition API, and don't liked it at all first time. Whenever I need to go and fix some bugs in old Vue 2 app without CompositionAPI and setup syntax - I feel very bad. Guess that Vue team a bit failed to properly describe why to use composition api, but now I think that it seems to be useful a lot
ttty 5y ago
I still don’t understand what’s so interesting about it… why you wouldn’t just write js that you already know? Instead choosing to use strings to code… ugh
rk06 5y ago
Most likely due to vue 2 to 3 transition. Vue 3 introduced many improvements and breaking changes. This also made many libraries lose compatibility with Vue 3. Not a good thing. While vue 3 was soft launched a year ago. The transition is still happening. With Vue 3 becoming default last week(feb 7). And major vue frameworks (vuetify and nuxt) just still working to support vue 3. I expect satisfaction to increase next year, when ecosystem catches up. And dissatisfied folks switch to other options. One thing to note is v2.7 is still shrouded darkness. Now, that major vue 3 work is done, Clarity and good support on v2.7 will also improve satisfaction.
- samwillis 5y ago
  Vue 3 is Vues "Python 3" moment, give it a couple of years and it will be mostly forgotten. Just as Python changed its string type to Unicode breaking compatibility, Vue changed the reactivity system. The other changes in Vue3 wouldn't fundamentally break compatibility on their own but made sense to fold into a big overhaul, just as Python did with various other changes in v3.
conradfr 5y ago
Maybe the Vue 3 transition and its composition API.
neurotrace 5y ago
Unpopular opinion here: the more I use Vue, the more I realize that it started off doing things differently because it thought it was smarter than more established frameworks. Over time, you're seeing it copy a lot ideas from other systems because they're actually hard earned lessons. Vue is the manifestation of the frontend hype cycle. There's no reason to use it over something like React which is much better supported
- pier25 5y ago
  I started using Vue back in 2015 and I agree. It's sort of a middle ground between React and Svelte with too many ways to do the same thing. Imo the best use case for Vue is as a jQuery no build replacement. Preact is also another good option for this.
  - synergy20 5y ago
    if to replace jquery, I will use alpine.js instead, which, is a much simpler vuejs
- solarmist 5y ago
  How does the Vue 2/Vue 3 change factor into your opinion? Making things more consistent or something else?
- midrus 5y ago
  Agree, used it for about half a year at a previous job. It tries to copy everything from everywhere and creates too many ways to do the same thing. The ecosystem is a lot smaller and many times I ended up on issue comments or readmes in chinese, which din't make it any easier. Also I got pretty pissed off with the 2 -> 3 transition, not as easy as they claim on big projects with real business pressure like to stop development for weeks during migration. Also Next.js is incredibly better (and better managed) than Nuxt. I'm never using it again.

sgdesign 5y ago

I think every framework sees this kind of drop once it gets widely adopted. Probably a combination of being confronted with real-world use cases, as well as the appeal of newer solutions that promise to do the same thing even better.

killingtime74 5y ago

It’s just the hype cycle. It’s only improved in recent years

nawgz 5y ago

Vue.js is heavily magic and doesn't support basic React concepts like render props. How is that possibly a popular framework? Like any "easy" library, you'll run into hard situations with no solutions.

searchableguy 5y ago
What do you mean? Vue has slots which is similar to render props. https://vuejs.org/guide/components/slots.html#scoped-slots https://vuejs.org/guide/components/slots.html#scoped-slots
- nawgz 5y ago
  After a read, I guess it does. A developer I respected claimed it was not easy to pass components down like this. Now I no longer respect him. Also, I still don't respect vue. Look at this abomination <MyComponent v-slot="{ text, count }"> {{ text }} {{ count }} </MyComponent>
  - pcthrowaway 5y ago
    You can respect that developers you respect are humans who make mistakes and misunderstand things. As you've done, you've made an inaccurate claim and learned from it. Hopefully you still respect yourself. Also (and I'm not familiar with Vue to know if this is the case), the state of software is such that you can make a claim and have it invalidated a few days later after an update comes out.
    - nawgz 5y ago
      > You can respect that developers you respect are humans who make mistakes and misunderstand things No I can't. Seriously, it was a joke, he's my best friend, but I guess I misunderstood his claim or he misunderstood render props! From what I can see reviewing Vue's 2.x docs, they seem to have had this "slots" idea for a while. I get a little bit ill from looking at that syntax though so I think I'll refrain from arguing about the library again!
AlfeG 5y ago
I understand all this traction with Composition API, and don't liked it at all first time. Whenever I need to go and fix some bugs in old Vue 2 app without CompositionAPI and setup syntax - I feel very bad. Guess that Vue team a bit failed to properly describe why to use composition api, but now I think that it seems to be useful a lot

ttty 5y ago

I still don’t understand what’s so interesting about it… why you wouldn’t just write js that you already know? Instead choosing to use strings to code… ugh

rk06 5y ago

Most likely due to vue 2 to 3 transition. Vue 3 introduced many improvements and breaking changes. This also made many libraries lose compatibility with Vue 3. Not a good thing. While vue 3 was soft launched a year ago. The transition is still happening. With Vue 3 becoming default last week(feb 7). And major vue frameworks (vuetify and nuxt) just still working to support vue 3. I expect satisfaction to increase next year, when ecosystem catches up. And dissatisfied folks switch to other options. One thing to note is v2.7 is still shrouded darkness. Now, that major vue 3 work is done, Clarity and good support on v2.7 will also improve satisfaction.

samwillis 5y ago
Vue 3 is Vues "Python 3" moment, give it a couple of years and it will be mostly forgotten. Just as Python changed its string type to Unicode breaking compatibility, Vue changed the reactivity system. The other changes in Vue3 wouldn't fundamentally break compatibility on their own but made sense to fold into a big overhaul, just as Python did with various other changes in v3.

conradfr 5y ago

Maybe the Vue 3 transition and its composition API.

neurotrace 5y ago

Unpopular opinion here: the more I use Vue, the more I realize that it started off doing things differently because it thought it was smarter than more established frameworks. Over time, you're seeing it copy a lot ideas from other systems because they're actually hard earned lessons. Vue is the manifestation of the frontend hype cycle. There's no reason to use it over something like React which is much better supported

pier25 5y ago
I started using Vue back in 2015 and I agree. It's sort of a middle ground between React and Svelte with too many ways to do the same thing. Imo the best use case for Vue is as a jQuery no build replacement. Preact is also another good option for this.
- synergy20 5y ago
  if to replace jquery, I will use alpine.js instead, which, is a much simpler vuejs
solarmist 5y ago
How does the Vue 2/Vue 3 change factor into your opinion? Making things more consistent or something else?
midrus 5y ago
Agree, used it for about half a year at a previous job. It tries to copy everything from everywhere and creates too many ways to do the same thing. The ecosystem is a lot smaller and many times I ended up on issue comments or readmes in chinese, which din't make it any easier. Also I got pretty pissed off with the 2 -> 3 transition, not as easy as they claim on big projects with real business pressure like to stop development for weeks during migration. Also Next.js is incredibly better (and better managed) than Nuxt. I'm never using it again.