Well, the Vue team aren't friendly to criticism of Vue. See the 2->3 migration for starters.
I don't know many projects which would have done that.
I'm still not a huge fan of the composition api. It's like a weird version of React function components with different quirks. Maybe I just need to use them more and I'll eventually get it.
Evan: They’re like, “Oh, Vue has scalability issues. We have a huge Vue product. We have these huge components that nobody wants to touch anymore. We don’t know how to extract and reuse things. TypeScript support isn’t great.”
Adam: So they started Vue 3, right? A breaking change. Vue had to stay relevant. People were looking for a scalable, if more complex, framework. Expectations had changed.
Evan: They’re like, “Hey. You’re taking away the very reason we love Vue, and it’s not going to be Vue anymore.”
In a way, our early user base are mostly people who preferred lightweight solutions, simple interactions, simple apps.
So when we propose solutions to address these more advanced cases, these simple case users get pissed off because they’re like, “Don’t touch my framework. I don’t want to work that way.”
“I don’t care about these complex cases. Why are you adding these complex APIs? Why are you making things more complicated?” But at the same time, these complex case users are like, “I won’t use Vue if it stays only for simple use cases because it shows it doesn’t scale. We are gonna just migrate to React, migrate to Angular.”
[discussion continues for a while https://corecursive.com/vue-with-evan-you/#composition-api]
I am in the middle of a massive Vue 2.6 (yea, they didn't even try 2.7 because change is hard) to Vue 3 migration and most of my problems have nothing to do with Vue and everything to do with an army of very opinionated people making all the wrong choices in the name of conformity.
That’s absolutely normal. There is no major effort ever in the history of software that was absolutely perfect.
But the most upvoted comments almost always tend to be focused on those specific mistakes/tradeoffs to the detriment of the larger goal and effort. They completely decontextualize the criticism from the fact that it may be a trade off or just a simple mistake.
And honestly, if I was to submit my closed source project and saw those criticism, I wouldn’t like it, but I could at least understand it.
But it must be ridiculously frustrating for Open Source software developers to have put in all this effort and then have everyone Monday morning QB on HN once the work has been largely completed when they could as easily have gone to the project GitHub or community pages and shared their feedback constructively when it actually mattered and could have had an impact on the direction of the product.