11
arcmak
76d

FUCKING HATE VUE 3

It's pointless, it's not an incremented version of Vue 2, it's basically a completely different framework, probably one nice to start a project with... But migrating from an existing Vue 2 project to Vue 3...

What the hell were they thinking!

first, setup() with all the logic and functions in it DOESNT MAKE ANY SENSE to me!
second, your old DEPENDENCIES NO LONGER WORK!.. good luck finding replacements for EVERYTHING, and do the necessary adjustments to work with the LASAGNA CODE YOUR PROJECT HAS BECOME!!

PS: the update/upgrade PR has almost 300 changed files!!!!

Comments
  • 8
    Least bad javascript framework
  • 5
    They seems to be trying the angular roadmap.
  • 3
    Well, yes. It's a pain to upgrade large projects, but it's also a major version. It's supposed to be breaking.

    It's also the same core as it's always been. It's the API that's changed, and you can still use the old options API if you so wish.

    Lastly, if you litter your setup with functions you're already using the composition API incorrectly. Organize your logic with composables and suddenly you've got clean code. If you don't like it that way, use the options API instead.
  • 4
    Agreed. I tried to use v3 for a recent project and nothing supports it yet.

    They're working on it, but v2 is still the "stable" build IMO.

    It's going to be a nightmare in a year when v2 community support plummets because of the huge paradigm shifts in the framework.

    Personally, I hate v3. It's just angular all over again. What happened is the angular devs got pissed about all the TS bullshit and left to find something new and now they're ruining Vue.

    It was never meant to be a hugely complex and overly complicated framework, but that's what the JS community wants.

    The JavaScript dev community is one big circlejerk, prove me wrong.
  • 3
    Felt so too (-> https://devrant.com/rants/3904058/...), and I must say, the more I use it, the more I like it.

    Composables are the way to go, if you don't use class components. If you do, Vue3 doesn't make any difference.
  • 1
    I've been using Vue 3 for 8+ weeks now and it's been much better than Vue3.
    It feels much cleaner.
  • 1
    @sariel +100 for your statement about the JS community.
  • 2
    With Vue 3, the only thing that seems game-changing to me is getting rid of mixin soup. I'm glad that Evan and co. took this route.

    However, it's hard to convince me to jump from Svelte now! ☺
  • 2
    @vintprox and this is exactly what is wrong with the frontend dev mindset.

    As a dev we have a responsibility to ensure that the frameworks we leverage are stable and supported long term (5+ years).

    As soon as something goes wrong with a framework that a dev or a team doesn't like, it's abandoned or entirely rewritten in a new hot framework.

    How many frontend frameworks are we going to have? Can anyone even list them?

    Angular js
    Angular
    React
    React native
    Vue
    Vue 2
    Vue 3
    Svelte
    jQuery
    jQuery UI
    Ember
    DoJo
    Backbone
    Semantic
    ...and these are just ones I know of through my peers and online searches.

    How many more will it take before we stand up and say no more. Just make one fucking framework and build it extensibly.
  • 0
    Takes time to get used to it ofc. But vue3 is sooooo much better.
  • 1
    It seems like there are wayyyy too many Vue projects that turn into jumblefucks of code.
  • 1
    @phat-lasagna I think the majority of those are angular or react devs that build monolithic frontends are trying to do the same in Vue.

    It's not only extremely difficult to do, it's not even recommended.

    Vue does great at domain driven design. Example: you have an e-commerce site that allows you to buy and sell cars.

    You have one Vue project that handles each of the following; user & account management, car inventory, selling, buying, support & forum, complaints, billing, etc...

    You have inter-dependancies handled through plugin design and installation.

    But that's not how you design in react or angular. In those two, you design a clusterfuck of a monolith that is filled with thousands of files nested deeply so far down nobody new will ever know how it works.

    This may not be the intent of those two frameworks, but I have seen it done this way dozens of times.

    Why? My theory is the "bolt on" tactic of most dev teams. Easier to bolt on than create from new.
  • 0
    @sariel 100% - I am not good at Vue by any means, but I really have seen this problem with Vue projects in continued maintenance.
  • 2
    @sariel @phat-lasagna Vue and Angular guides state that you should never abuse or overuse Input/Output patterns.
    It's not the framework's problem if (ab)users do their daily shitfuckery... As everywhere else in programming, it wholly depends on the coders to create readable and maintainable code, no framework can fully solve that.
  • 3
    @sariel @phat-lasagna Funnily enough - relating to this thread - I stumbled upon a review a "dev" has done on TailwindCSS in which he claimed, after testing it for 10 minutes, that it is allegedly utter shite and that "Tailwind forces you to write every helper class inside HTML class attributes", which is of course a dumb lie, but neither comments making him aware of that could change his mind. He'd most likely be one of these devs who clusterfuck their way through frameworks and mimimimi the whole time why there is "no good" framework lol
    I wasn't relating this to you two but wanted to show an example.
  • 0
    I agree on this one. They could've named it something like "Vue Next" after all.
  • 2
    @PonySlaystation yeah fs. I believe there is no good or bad in any technology. Only the relation between the humans and the technology produces good or bad results. Although, when I do hear tailwind, I usually get a sickening feeling in my stomach and run away lol.
  • 0
    @PonySlaystation but is a framework shit because the devs and community is shit?

    Support is shit, so IMO the framework is shit.

    You could attempt to build the most advanced application with that helps bring world peace, but if you don't get the support from the community on it to do so you will never achieve your goal.

    I don't disagree, but just want to enunciate that WE are the problem.
  • 1
    Coming from a react based web app, vue 3 has been pretty nice to work with. Vue 2 looks like another “$” dumpster fire lib.
Add Comment