15 ms·
Vue 3 as the New Default
- randomsearch 5y agoWorth noting that major frameworks have yet to update for Vue 3. Make sure you check all your dependencies before embarking on that course. I like Vue 3 so am finding this seemingly slow adoption to be a real pain.
- FinalBriefing 5y agoHopefully now that it is the default, more UI libraries will focus their efforts on it.
- DaiPlusPlus 5y agoSome day, eventually, after all the dust settles in the JS ecosystem, there will be a stable framework for managing UI state in a sane, sensible, predictable and well-understood manner - and someone at the WHATWG/W3C will finally write up a spec and the functionality will be baked-into Chrome, Edge, Firefox, etc. And we'll be free from having to learn a new JS framework every 6 months. And maybe even npm hell too. Until then, time to buy another Pluralsign training course...
- nikanj 5y agoMeanwhile my Swing skills from the 1990s remain relevant today. Java might not be hip, but it sure does get the job done for enterprise apps
- topicseed 5y agoNPM hell is what got me to move from beloved TypeScript to Golang. Coming back to pet projects a few months later was true excruciating pain every single time. Today, it's Go in the backend and Svelte in the frontend, or vanilla JS for very small and simple tools.
- ashishb 5y agoAs someone who programs on backend, frontend, and Android apps, I can't agree more. Javascript frameworks and NPM hell is terrible. You rarely have the problems in Go/Kotlin/Java world that are considered normal in the NPM world.
- adevx 5y agoI never understood this npm hell reference people are speaking off. Is this just the drama of updating an outdated inherited project? I've been working with node/npm since the early days and don't consider it worse than what you find in Java, Python or PHP.
- ashishb 5y agoThe latest version of webpack removed polyfill, this broke another dependency, and i had to downgrade the react version to fix that! Nothing like this did I ever see in the go or kotlin world.
- qmmmur 5y agoIf you depend on a specific behaviour why dont you pin your react version?
- ashishb 5y agoI learnt that much later. Apparently the current version of webpack that you get by following the official react project setup is missing certain polyfills!
- zero_shift 5y agoCouldn't you have pinned your dependency and / or installed from a lockfile?
- jrib 5y agoare you leveraging a framework on the backend for Go?
- arnvald 5y agoIs is really that bad? I'm not very up-to-date with JS frameworks, so please bear with me. I know that new libraries pop up here and there, but if I'm not wrong, React is by far the most popular, and React has been around for almost 10 years. Vue's not much younger, and now it's 3rd major version. Is there such a big difference between JS front-end frameworks and the rest of the world?
- EMM_386 5y ago> Is is really that bad? It's not that bad. I am lead on a large Angular 13 project and we love it, easy to work with, build, deploy. We have literally no issues at the moment. .Net 6 C# APIs on the back-end, Oracle database. It just works. Take everything with a grain of salt.
- oblio 5y agoHow is internationalization? Last I asked, it was still a tire fire, even after more than a dozen versions and after a fully mature previous framework that was replaced :-(
- FinalBriefing 5y agoYea...Angular made a huge (and hardly documented) change to their internationalization library that forced us to migrate to a third-party one. Basically, they now (as of Angular 12) force you to build a difference version of your app for each language you support, and either serve them up at different URLs or use cookies to serve up the right version to each user. The technical reasons make sense...your translations occur at build-time, rather than at run-time, but it's a pretty drastic change that occurred out of nowhere. Not a fan.
- ipaddr 5y agoHardcoding a language variable into multiple builds?
- tlrobinson 5y ago
- lmarcos 5y agoI don't think that's gonna happen. The same way modern browser's don't come with a java runtime to run servlets. Something better (and different) will come after SPAs, and the cycle will start again.
- DaiPlusPlus 5y ago> The same way modern browser's don't come with a java runtime to run servlets. Servlets run on the server, I think you meant applets? If so, I'd argue a counter-point: WASM and <canvas>.
- ioseph 5y agoWhat new framework is being widely adopted that was released in the last 6 months? The most recent one I can think of is Svelte which came out 2016.
- whalesalad 5y agoI use Vue 3 without the new composition api. It looks and feels more or less like the old Vue. I actually think things are pretty great these days. Even amongst the different frameworks and tools, things are settling into a common set of ideas and concepts. If you made the choice to build an app on React/Vue a year or two ago, that decision is still valid today and I think that speaks a lot for how far things have come.
- slig 5y agoAnd then it will become "old", exactly like Django/Rails feels today and the wheel will be reinvented with something "better" and more complex.
- powersurge360 5y agoI have been _very_ bullish and excited on LiveView and its cousins from other platforms. Hotwire was the first time it's entered my personal dev world and I've been working on a hobby trivia app since Christmas and it has been an absolute _joy_. It's obviously not a one to one replacement for an honest to god frontend application, especially one that can be recompiled into an offline capable native app, but where you can use it, it does a lot of lifting.
- root_axis 5y agoThis comment is just low-effort complaining that we see on every JS thread on this site. Vue 3 is an option you don't have to use, same as React, Svelte or just jQuery. The implied suggestion that nobody should ever publish new code is tiring.
- DaiPlusPlus 5y agoYes, that was half of my post - but the first half is my hope that eventually the functionality from React/Vue will be built-in to the DOM (or at least baked-in to the browser). We're already half-way there with WebComponents (though I'm not a fan of WebComponents as-is, but that's a tangent). Also, I still believe that web-pages should be functional without JavaScript. For all of my traditional SSR / non-SPA projects I definitely put effort into ensuring my projects exhibit graceful degradation. There's already a lot of things we can do without any scripting at all: animations and dynamic content, for example - and we can even use CSS trigger-tricks for basic interactivity (e.g. show/hide toggles) all without scripting. What I'd love to see next is something like WPF/XAML's declarative data-binding in HTML (but in a less broken way...) - and I'd like to be able to submit a <form> element directly as JSON, as well as AJAX-like <form> submissions that don't replace the current document, all without scripting - that's the dream (oh, and CSS positioning relative to an arbitrary named element, I could go on...).
- dceddia 5y ago> We're already half-way there with WebComponents (though I'm not a fan of WebComponents as-is, but that's a tangent). I think this is actually not a tangent at all, but rather, it’s kinda the whole point! I doubt we’ll ever get to a point where there’s a single standard, because a single standard can’t satisfy everyone.
- dham 5y agoIt's already invented. It's called HTML. You then use whatever language you want to generate it. We were doing it a long time ago with Java Server Faces. Now there's stuff like Liveview and Turbo (Rails community)
- visarga 5y agoThat's how great humans are at generalization, just 10 years of collective search and we reached the web UI enlightenment. /s
- turndown 5y agoWhat do you think of htmx[0]? It feels like something that could actually fit into the HTML standard. 0: https://htmx.org/ https://htmx.org/
- tokumei 5y agoHow does the custom script syntax work? E.g. ‘on click call some_func()’ Is there really a JS script parsing all of that? Seems like there would be performance penalty.
- irrational 5y agoThis is me. I really don't like using frameworks/libraries and want it to get baked into the standard library.
- themacguffinman 5y agoWhy are people so obsessed with finding one true way to do everything until the end of time. Things change, things become more diverse, and the world is richer for it. There already are sane, sensible, predictable and well-understood frameworks for it, it's called Vue, it's called React, etc. You don't need a committee to bless it before you can enjoy such a stable environment. This is a lot like the 19th century US Commissioner of Patents saying "Everything that can be invented has been invented." Society and technology won't sit still. It's your choice to learn a new JS framework every 6 months. If you don't want to use the new thing, then don't. Just make something valuable and use what suits your needs. That's all that has ever mattered.
- notapenny 5y agoIndeed, focus on what to build and how to build it. What you build it in is largely irrelevant.
- dham 5y agoIf W3C would stop doing initiatives like Web USB and give us a way to style a select box (finally going to be a thing) we wouldn't even need web frameworks. * Styled select boxes * Good cross platform datepicker with ranges that looks good * More form validation options / dynamic form validation * A good drag api that does edge detection well in every browser * Bring back frames (would allow good nested routing) * A built in rich text editor * A good modal API (or bring it back) * A way to submit a form via AJAX with just a property (think Rails UJS) to just render html.
- justsomehnguy 5y ago> and give us a way to style a select box How many end-users complained what a select box is not styled?
- dham 5y agoI hear you, that's another thing that has plagued our industry. Most of the time a regular select box is fine, but sometimes you need to have images or something more in the options (colors, etc)
- brimble 5y agoNone, probably, but these days it's de rigeur to spend half a (web or mobile) project's budget making sure even the select boxes are "on brand" and "delightful" or whatever. Often at the expense of usability.
- andrei_says_ 5y agoStyling a radio button, a select box and a slider would be amazing, too. Now the only option is to replace them which is quite sad.
- dham 5y agoYea you're right, that's like the biggest one. Can't believe I forgot that.
- 5y ago
- eBombzor 5y agoWhy pluralsight specifically?
- DaiPlusPlus 5y agoI get Pluralsight for free with my MSDN subscription
- pcurve 5y agoThe messed up ecosystem keeps millions of people employed!
- wldcordeiro 5y agoYeah because people stopped developing any backend solutions for Python or Ruby because Django and Ruby on Rails exist.
- rr808 5y agoI think best to skip JS and go straight to webassembly.
- dwaltrip 5y agoLikewise, one day I will achieve transcendence and suffer the ills of the human realm no longer. I'm totally on board with building better tools and solutions. And with pointing out the flaws of tools as we find them. However it is folly to thing this work will ever end.
- deleted 5y ago[deleted]
- zero_shift 5y ago> We'll be free from having to learn a new JS framework every 6 months The de facto starting point for writing browser applications is React, and that came out almost nine years ago.
- yurishimo 5y agoIt’s hilarious you say this as React is arguably introducing the biggest paradigm shift since hooks (which was also a huge change) with Suspense. It’s fine to say React is a decade old but the way we write apps with React has drastically changed multiple times with the only real constant being JSX. And let me be a bit proactive, yes, I know react is backwards compatible for the most part, but similar to PHP, just because the syntax is still supported doesn’t mean that’s the recommended way to write apps today. React arguably started the churn of JS fatigue we all complain about now.
- mikewhy 5y ago> the way we write apps with React has drastically changed multiple times with the only real constant being JSX I don't really agree with this. Sure, we went through createClass -> class -> functions + hooks, but the core is still props, state, and lifecycle.
- yurishimo 5y agoEh, agree to disagree. I understand your point, but I think those points you mentioned are also changing. Take lifecycle. It used to be very explicit. Then hooks turned it into this weird implicit thing where you have to know how use effect works and how to only trigger something once, but then the empty array thing is an anti pattern etc etc. Now with suspense, that lifecycle is changing again in a way. I’ve seen some tutorials where the teacher refactors out of use effect into throwing a promise. But then you can have use effects inside your thrown promise and dealing with module scope potentially. It’s late and im a little out of it, but to me, this is all a lot of churn and creates long periods of uncertainty as developers try and decide which of these features they want to use and when. At a certain point it can get really frustrating when it feels like you need to rewrite your app to stay up with “best practices” and attract new talent into your org. It would be one thing if the best practices were making things better functionally, but I find that argument hard to justify for anyone outside of Facebook scale. Angular and Vue stuck with a more traditional lifecycle ideology and there are plenty of apps building at scale on those frameworks. That stability in low level APIs gives a community time to grow and mature without leaving a bunch of people behind. I honestly believe React would not be anywhere near the scale of what is today based on merit alone. They were lucky to see the demise of angular 1 and learn from that mistake and now Vue is sorta suffering the same way by moving too far away too quickly from 2 to 3. Anyway, ramble over! :)
- _prototype_ 5y agoReact already has us there
- forgotmypw17 5y agoI think we already have it, and it's called DOM, CSS, and JavaScript.
- pjmlp 5y agoOnly if you want to play the game, there are plenty of jobs using vanilaJS and <script ...> still works.
- notapenny 5y ago"And we'll be free from having to learn a new JS framework every 6 months" You are already free from this. The only one putting that pressure on you, is you. Pick something and stick with it, and spend your time learning _how_ to build things, instead of _what_ to build it in.
- spuzvabob 5y agoIf you are considering upgrading from Vue 2 with Vuex note that store getters caching is not working in Vuex for Vue 3, potentially hindering performance significantly. The issue was reported multiple times but it's not yet fixed: https://github.com/vuejs/vuex/issues/2102 https://github.com/vuejs/vuex/issues/2102 https://github.com/vuejs/vuex/pull/1883 https://github.com/vuejs/vuex/pull/1883
- FinalBriefing 5y agoStill! That's surprising.
- bussyfumes 5y agoThis is great news, Vue 3 looks much better than its predecessor. However, I had to migrate a Vue 2 + TS app to Vue 3 and their guide at the time was pretty underwhelming. Props to Evan for dedicating time to migrate a sample app and publish the migration as commits, but the app was quite basic and dependency-free so I had to figure out a lot of stuff on the go. The compatibility build actually slowed down my progress as it took me a lot to figure out that I didn't actually benefit much from it and could just drop it. Till this day I don't have a clear idea about what @vue/compat is for. Hopefully, with them pushing Vue 3 as the new default, there will be more detailed how-tos available.
- FinalBriefing 5y agoThat's been my experience, as well. I got everything working because I'm very familiar with Vue, but I did end up removing a lot of TypeScript from my app just to make it all easier. Luckily, Vue makes it easy to mix and match JS and TS (for better or for worse).
- adevx 5y agoI jumped on the React bandwagon because I didn't like the Typescript support in Vue 2, and did not see much improvements for V3. Vscode Vetur was slow and unable to do full typechecking in Vue files. Much of my code was based on Vue Class Components, which was not going to be compatible with the new API. Vuex did not seem to be going in the Typescript direction either. A bit sad if you consider Vue 3 is written in Typescript.
- rk06 5y agoVuex is going in direction of pinia. While Vuex has a v3 compatible build, it is there to ease migration, not as recommended for new vue 3 users
- zigomir 5y agoTS support has been improved dramatically with volar VSC extension and vue-tsc CLI tool. When that was released (I’d need to check when but in 2021 or even late 2020) my React FOMO disappeared as I get full TS support in script and template tags. Composition api + VueUse are wonderful together. I’ve been lucky to start fresh with vue 3 mid 2020 (in beta?). But I and can understand frustration to migrate. Having said that, I think it’s totally worth it.
- greencore 5y agoVue 3 perhaps is ready but not its ecosystem. Important libraries (like form management) port to v3 is still in alpha. It was one of the most painful development experiences because of that.
- The_rationalist 5y ago
- newsbinator 5y agoI can't use Vue 3 in production until Vuetify is close to ready (which it's currently not).
- Hawxy 5y agoSame. Vuetify v3 sadly got delayed yet again to Feb Beta/May GA.
- tmm84 5y agoThis was one of the things I was wondering about. Vuetify is one of the bigger libs for Vue2 so if I were to do some upgrades it would need to be ready.
- newsbinator 5y agoI tried Vuetify with Vue 3 about a month ago in case it was "semi-ready" and lots of basic functionality was still missing. As much as I love working in Vue, Vuetify is the entire reason I use Vue today: if there were a Vuetify for Svelte I'd be using that instead. All the Svelte component libraries, and indeed all component libraries I've ever tried, pale in comparison to Vuetify. With perhaps the exception of Quasar. Using Tailwind after Vuetify feels like going from writing C# to assembly.
- yeskia 5y agoIt's crazy how much of the ecosystem is behind, despite Vue 3 technically being available for a while now. Honestly think I'll be looking to migrate away from Vue instead of up to 3.x.
- hendry 5y agoI was dumb enough to use https://unpkg.com/vue https://unpkg.com/vue on my projects and now I have to deal with "Uncaught TypeError: Vue is not a constructor" this morning.
- phil-martin 5y agoSame here, I wonder how many apps around the world silently stopped working today. It was my own fault for not self hosting or not pinning the version, but it was still a surprise!
- sebazzz 5y agoShould unpkg have discouraged this and not offered unversioned urls at all?
- numbsafari 5y agoFolks shouldn't use unpkg.com. The only relevant discussion you can find regarding a privacy policy is a twitter thread that ends with the developer saying "I really should discourage adoption because it's getting too big." No dig on them, but, really... at some point we need to start doing a better job of owning this stuff.
- tosh 5y agoSame here, this is how I found out about Vue 3 related: The mess we're in (a talk by Joe Armstrong) https://www.youtube.com/watch?v=lKXe3HUG2l4 https://www.youtube.com/watch?v=lKXe3HUG2l4 (yes, I know, I should have vendored the dependency in the first place)
- ramesh31 5y agoCan someone make a convincing argument for me to adopt Vue that doesn't involve "it isn't React"?
- Rodeoclash 5y agoI've used both extensively now. Out of the two I prefer React. I'd describe Vue as more bells and whistles, less safeguards. I think developers prefer Vue because it doesn't get in your way like React does (despite React having very good reasons for getting your way!)
- FinalBriefing 5y agoInteresting. I've found that with Vue's ESLint rules, it has excellent safe-guards. Every React app I've inherited has been full of race conditions due to 'hooks'.
- The_rationalist 5y agoIt is significantly faster, see benchmarks. Also more concise/ergonomic and declarative.
- dham 5y agoIt's more sane. It does fine grained updates without having to manually optimize like in React - useCallback/useMemo/React.memo/splitting components. Think of a list view where you want to update a single item in a list. People generally understand Vue better because you can just push to an array and it reacts to it properly without having to commit to the React immutable data religion. Basically if you were to competently build a framework you would have Vue, if you were trying to impress your colleagues and bring up bullshit comp sci principals so you can write 50x more lines of code while spending 100 hours trying to optimize a list re render, you would have React. After using React professionally since 2015 I've come to the conclusion: Only very few people at companies actually understand React beyond the surface layer. Everyone else just kind of gets by because on the surface it seems simple. It's actually really really hard to build performant React apps, but most developers are naive because they have $4000 mac book pros and Chrome cpu throttling isn't cutting it anymore. It's really an infection that has spread through our industry.
- keithnz 5y agoI recommend looking at Vitesse :- https://github.com/antfu/vitesse https://github.com/antfu/vitesse Even if you don't like the exact setup , you can customize it to your liking (and there are a number of forks that do exactly that), but it puts together quite a few things that you often want as an "out of the box" experience.
- FinalBriefing 5y agoThanks! I like having these to compare my projects to.
- jmull3n 5y agoThank you, I was looking for something exactly like this yesterday. How does it compare to Nuxt 3?
- FinalBriefing 5y agoDifferent tools, I think. Nuxt is like a framework for your framework. vitesse looks like it is just a template to start any Vue 3 project with.
- keithnz 5y agoThis plugs together some of the nicer features from Nuxt 3, and other toys by adding the necessary plugins to your vue 3 project, Nuxt 3 is more of a whole toolset / layer on top of vue 3, but having played a bit with it, its not really ready (which is essentially what they say also). I'm guessing once Nuxt 3 is stable and released, it is going to be well maintained as a cohesive set of features, where this is more of an opinionated configuration of plugins as a starting point.
- jackconsidine 5y agoI get the impression that Vue 3 was a greater effort than expected. It was talked about for years before beta release (on Full Stack Radio, for example). March of 2020, I was at Vue Conf (days before Covid lockdowns began), and I heard a few people complaining that this wasn't the expected official Vue 3 release. Here we are almost two years after that and it's just becoming the default. That said, I understand that there were monumental under-the-hood improvements, some of which spawned off Vite.
- FinalBriefing 5y agoI'm surprised, too. I'm happy they took their time as Vue 2 was/is still a great framework, but I probably would have chosen Vue 2 for some projects had I known it would take this long to get Vue 3 out the door.
- russellbeattie 5y agoSecond-system syndrome. * Even if you think you're making sure to not fall into the trap, it always happens. The first version solves a specific problem and has enormous success, there might be some cleanup (v2), but then the Big Rewrite is going to clean up all the little issues and add in some highly requested features which will be so much easier because of the new architecture, programming language, etc. You estimate about six months, tops. Then three years goes by. I find the phenomenon amazing because I've experienced it personally and it's maddening. All the hours spent talking about the second system trap and planning how to avoid it had absolutely zero effect on it actually happening. It was like a black hole void where you just kept making one step forward and two steps back. 1. https://en.m.wikipedia.org/wiki/Second-system_effect https://en.m.wikipedia.org/wiki/Second-system_effect
- rk06 5y agoIt was great effort. It included reactivity internals updated to proxies, composition api, typescript support, EJS modules adoption etc. and all that including surrounding core libraries and docs.
- tambourine_man 5y ago>From a Library to a Framework What I liked about Vue was that it was a simple view library. Yeah, there it goes. There seems to be a hatred towards simple tools in our generation that I can't fathom
- o_m 5y agoI recommend checking out Alpine.js which looks and feel like Vue 1. They don't have any ambition to be anything more than that. https://alpinejs.dev/ https://alpinejs.dev/
- lbbenjohnston 5y agoAlpine actually uses the Vue reactivity model under the hood. I like the idea of it but for what I work on the CSP non-compliance is a deal breaker (their CSP compatible build is not ready and you lose most of the alpine benefits). https://alpinejs.dev/advanced/csp https://alpinejs.dev/advanced/csp I think that Stimulus JS offers many of the same benefits and provides a nice abstraction for making one 'element' contain multiple behaviours. https://stimulus.hotwired.dev/ https://stimulus.hotwired.dev/
- newlisp 5y agohttps://github.com/vuejs/petite-vue https://github.com/vuejs/petite-vue
- mythz 5y agoCan attest to how great petite-vue is, which we used to build ServiceStack's new API Explorer: https://docs.servicestack.net/api-explorer https://docs.servicestack.net/api-explorer Originally we started out with VanillaJS & hand-rolled MVC pattern however the productivity slowed as the App was getting larger, switching to petite-vue was a major productivity boost giving us a productive reactive UI, ability to componentize our App into modular components & resulted in the fastest UI we've seen in a client UI.
- mort96 5y agoI reject that it's specific to "our generation". The people who made the monumental balls of complexity that Java is known for certainly aren't part of "my generation" at least. And we have contemporaries who embrace simplicity in significant and impactful ways.
- npunt 5y agoGood news! I hope the focus can shift to the ecosystem now. Two friends of mine have big projects that are stuck on Vue 2 because of Vuefire.
- ramesh31 5y agoI've got a real sour taste in my mouth over Vue. React is the industry standard, and it's what the overwhelming majority of libraries, frameworks, documentation, and tooling around front end web development is geared towards supporting. People use React because it's the right tool for the job, and they have no real strong opinions about it either way. But people use Vue for ideological reasons. For some opinionated reason or another, they take issue with using a framework created by Facebook or they have some silly little nitpick about a particular detail of the API that they use to justify their zealotry. My company is now full of these "loud minority" ideologues that have successfully lobbied the entire engineering organization against React. The majority who preferred React were silenced, because they are not ideological about their technology choice and would rather just placate the people taking issue with it. And now we're rewriting perfectly functional software to be more "standardized" with the rest of the company in Vue. It's insanity.
- FinalBriefing 5y agoI'll take the bait. There's certainly no industry standard for JS frameworks. It might be in your circle, but that's certainly not the case in the industry. In my experience, I've found Vue to be a lot easier to learn and to teach to others. I can task a junior developer with a new feature in Vue, and generally speaking, the biggest changes are to simply break large components up into smaller ones. Meanwhile, I've inherited several React apps developed by shops that focus on React, and they all have weird race conditions due to 'hooks', and all sorts of code that breaks web standard. I know a lot of people out there are very productive with React, but in my experience, the whole process is much more enjoyable when working with Vue. Neither Vue nor React are the only solutions out there, and it's important to not be too dogmatic about which tools people choose to work in.
- adam_arthur 5y agoPeople (Myself included) like Vue for real and valid technical or ergonomic reasons. Explained some of my reasoning on your other thread, and I'm sure others have a different set of reasons that are perfectly valid too.
- pier25 5y ago
- newlisp 5y agoBetween react and vue, which is better suited for adding dynamic components here and there to a server-side-render html webapp?
- Ronsenshi 5y agoIf you're choosing between those two, then I find Vue still better at this than react, where you have to go full JS rendering. Vue 2 had inline-template support which allowed progressive enchantment of HTML. Vue 3 however dropped support for that (there are few workarounds). All in all both frameworks aren't too great at sprinkling dynamic functionality on server-side rendered HTML.
- newlisp 5y agoFWIW, just found this https://github.com/vuejs/petite-vue https://github.com/vuejs/petite-vue while skimming vue's website. Why do you think they are not great at this?
- Ronsenshi 5y agoIf we consider Vue 3 and React - they are not great at progressive enhancement because they are not built for that purpose if you're not using corresponding server-side renderer. If your backend return simple HTML - there's no way to mount Vue3 or React on top of that HTML and be sure that it won't be fully replaced by JS-rendered HTML because it has small differences between them. Vue-Petite is definitely interesting and I likely will use it in the future, but talking strictly about Vue 3 and React - they are more suitable to SPAs than to progressively enhance your HTML.
- samwillis 5y agoHalving spent a fair bit of time with Vue2/3 and coming from a Python background. I think to some extent the Vue2 to 3 transition is quite a bit like the Python 2 to 3 transition. It’s a big change, some controversial decisions, and the ecosystem is taking quite a while to catch up. However just like Python 3, Vue 3 is a massive improvement, I love the new competition api. I think it’s a great success and they made the right decision to push through with it.
- agumonkey 5y agoLatest Evan You talk wasn't met with a lot of praises. Especially the adhoc syntax to expand reactive values.
- CharlesW 5y agoIs this the one you mean? https://www.youtube.com/watch?v=2KBHvaAWJOA https://www.youtube.com/watch?v=2KBHvaAWJOA The comments there don't seem particularly negative.
- agumonkey 5y agoI had this reddit thread in mind https://old.reddit.com/r/vuejs/comments/s3595h/the_new_vue_by_evan_you_vueconf_toronto_2021/ https://old.reddit.com/r/vuejs/comments/s3595h/the_new_vue_b... I can't say I disagree, vue3 felt like a react metoo-release, and now it looks like some features are temporary deadends requiring more tricks to manage.
- neovive 5y agoIn some ways, Vue is a victim of its own success. I enjoy working with Vue and will continue to support the framework as the transition to version 3 continues. Ultimately, tough choices need to made and I understand the pushback from long-time users that depend on older features. (I use the term "old" loosely, since time and legacy in the front-end JS is skewed.) Like Python 3, the essence of Vue remains in Vue 3 and the framework will move on.
- jmuguy 5y agoI feel like we’ve been trapped between Vue 2 and 3 for a little while. A lot of libraries and wrappers have not been updated for use with 3 and I’m not good enough with JS to try forking and updating them myself. And then there’s stuff we’d like to use (like Headless UI from the Tailwind folks) that’s only available for Vue 3.
- fl2100 5y agoAnyone who has used both Vue 3 and React that wants to share their experiences? Which framework do you prefer overall (including dev experience and ecosystem support)?
- ng12 5y agoReact has the bigger community and therefore tends to be better supported. Otherwise, the two are almost identical.
- Jcampuzano2 5y agoI've used both in a professional capacity. Vue botched their upgrade path to Vue 3 and now it's stuck in a similar limbo to Python 2/3. They "released" Vue 3 long ago but basically none of the ecosystem including officially supported libs like the Vue-Router/Vuex was ready and now a long time later many are still using Vue 2 because the ecosystem still hasn't caught up. The docs for Vue 3 when it was "released" were not good at all. I used to host a Vue meetup and was originally excited for Vue 3, but most of the people I talk to who use Vue in their projects are still stuck on Vue 2 and have no plans of upgrading due to most UI libraries still not being ready. Even though there is a core team now, it seems Evan himself has been less focused on Vue and moreso on Vite and tooling in general lately. I don't complain much because I love Vite, and no longer use Vue but I do know some Vue devs who are losing confidence. --- I use React daily and at the very least they have rarely if ever broken backwards compatibility without being very fair on the ecosystem in terms of the time needed to upgrade, and releasing experimental versions for people to test/play with. Both are similar when it comes to dev experience, both have dev-tooling and editor integration. Though TS support for Vue was always lacking behind React. "Vetur" which is the VSCode/Editor extension to get good support for .vue files worked well enough until your project grew beyond mid to large in size at which point it slowed to a crawl for every dev on my team. Didn't have this problem with React. I think there is a new extension for Vue nowadays though. Some of this is obvious a side-effect of there being many more devs working with React daily both in a hobby and professional capacity than Vue though.
- fl2100 5y agoThanks for your insights! I have used Vue on several projects before but I have noticed that the entire ecosystem is basically in a beta stage. Things are changing all the time. For example, the default state management solution just switched from Vuex to Pinia but a Vue 3 compatible version of Vuex still exist. Will it be the new default in one year? No one knows. It's the same thing if you want to use things like SSR and not implement them yourself. You can either use Nuxt and continue to use Vue 2, or you can use the non-production-ready Nuxt 3 beta, which supports Vue 3. Both aren't great options. Because of these issues, the strong community in the React camp really makes me consider switching to React for new projects.
- realty_geek 5y agoI moved from using vuetify with nuxtjs to using the quasar framework because they successfully moved to vue 3 and I haven't looked back. Quasar is hugely underrated
- atentaten 5y ago+1 for Quasar. I find that it allows me to get things done fast without having to think about and build boring and tedious components. It's easy to restyle or modify it's component library and I'm finding it quite nice. I wish there was a robust vue to native app tool available.
- ilrwbwrkhv 5y agoWhy does vue look more and more like react. What's even the point of having a different library then? I'll just use React if I need to write useX nonsense.
- as1992 5y ago> I'll just use React if I need to write useX nonsense. You don't need to. The options API still has 1st class support. The docs allow you to switch between composition API and options API.
- Jenk 5y agoIt started when React had that license fiasco some years ago, and Vue picked up a huge surge of new users as a result. They have, IMHO, been chasing that high ever since. Having said that, I still like Vue for a markup-first kinda of framework. React is code-first, markup later. I tend to favour using React for most development scenarios, however, as most are code-first - and also because there are a dozen React candidates for every Vue candidate in my experience.
- coding123 5y agoOur company was React (after that fiasco died down with React changing the patent/sue clause). About 2 years ago our new tech lead decided that we would use Vue instead. Ever since that decision I found myself walking more and more into backend development. I just felt like all the Vue code we wrote felt like I was writing 2011 AngularJS code. Not sure what people find so compelling about it. A month ago our tech lead decided we're going back to React for everything using Next. Everyone loves it. Everything is type safe and every variable has full type hints. Props are type hinted. It's great.
- Destiner 5y ago
- goodoldneon 5y agoWhy did your tech lead want to switch to Vue?
- hahamrfunnyguy 5y agoI am currently on Vue 2, but would like to migrate to Vue 3 at some point. I am curious if anyone has as used the TypeScript class syntax with the decorators. Last time I tried to migrate it, there were a bunch of things that failed. Presently it looks like one other dependency I need hasn't been migrated to Vue 3, either.
- 9dev 5y agoIn retrospect, I’m so happy I did not jump the class syntax bandwagon, that always felt a little suspicious. The best option seems to be migrating components to the (still supported) options API, which is arguably going to be harder if you have class style syntax you need to get rid of first…
- shrew 5y agoUnfortunately they pretty much dumped the class syntax early on in Vue 3's development, so you'll probably find it quite hard to transition to Vue 3 if you Vue 2 codebase is full on class components. I had a similar issue having adopted the class syntax and I think rewriting is probably the only way out.
- ghoomketu 5y agoHaving transitioned from Vue 2 to 3 the biggest thing I love about v3 is no need for `this.$set` anymore, as almost all properties are fully reactive now by default. Even after working on some rather big projects we never used composition API once. It feels more like a hindrance than an asset and greatly disrupts the simplicity of Vue, which is the most beautiful thing about it. But thanks to Evan's/team insight they've made it 100% option to use and so it didn't get in the way much. Overall the number of improvements in v3 are amazing and the new native elements like <teleport>, fragements, etc are god-send if you ever had to struggle with them in v2. I really wish they didn't remove the event handler ($on) though. That really made life very easy and using a separate lib for that is a bit of pain imo.
- beebeepka 5y agoLike many others, I wasn't a huge fan of the composition API. Felt like we were giving up many quality of life features in the name of a weird "must be like react" push. On the other hand, once I started actually using it, I found myself liking <script setup> very much. I also like the "ref" thing because I have been pushing for this approach for a long time. Values are objects/proxies is a wasteful, yet powerful approach. I am not going back to writing Vue 2 style components and encourage all of my co-workers 5o do the same. They are slowly but surely coming to accept it. No more lazy hacks for them
- udbhavs 5y agoI've had the same experience. The TypeScript support, explicitly defined reactivity so you have fine-grained control yet still simple and understandable code using the same models of computed, ref, and watch etc which anyone can grasp in no time. I know the churn in the Vue ecosystem is attracting a lot of resentment but I'm absolutely loving it. The Composition API is clean and effective and <script setup> takes it further to svelte-like succincity, Pinia builds on simple reactive state instead of the needless complexity of Vuex, Vite is fast, Volar finally brings type checking to templates and VueUse offers hooks for several little niceties that just make the experience more pleasant (https://vueuse.org/ https://vueuse.org/). The only thing I dislike is the macro based reactivity transform proposal which would auto add .value to special refs during the compile step, but that isn't even finalised yet and of course completely optional. It's a great time to be a Vue dev and I hope they continue developing 3 because even if it's not the same library it was, what we have now is too good to lose and I love using it.
- blindseer 5y agofwiw, I started using Vue 3 recently for a project and the new composition API + new script setup feature makes Vue 3 comparable to Svelte in a lot of ways in terms of lines of code. Script setup definitely reduces boilerplate and once I was able to wrap my head around it, I really liked that. That said, I don't think their documentation at the moment conveys why script setup is so useful (at the time of writing this comment). For example a lot of their examples in their documentation used their old API. In my opinion, script setup + composition API is really nice. I haven't used React in a few years, so I'm not sure how it compares, but using Vue 3 features decreases the number of lines of code you have to write and maintain (in comparison to Vue 2), and I'm generally always for that. I would go as far and say that they would officially come out and say that the old API is deprecated. I guess my only quandary is whether to use Vue 3 or just bite the bullet and use Svelte instead. If Vue 2 => Vue 3 is a decrease in 60% of the code, Vue 2 => Svelte seems to be a decrease of 65% ish. Is that extra 5% worth it? I don't know.
- sidhuko 5y agoI joined a company with a Vue app just before the Vue 3 release. I don’t think anyone believes it was a soft launch. Then the tooling like nuxt did the same with a v3 release countdown timer which only then released it was in beta with no support in their ecosystem. You could pay 10k for a consultancy though. I only wanted webpack v5 to be able to use federated modules to give us more migration options. The whole experience reminds me of Angular.js to Angular so I was quick to jump ship and spend the migration effort for v3 in moving to react. We spoke to a contributor too that basically told us we should wait for v3 because currently it’s not really built for SPA. Vue 2 was a web application framework and I could see the benefits for php/python/ruby frameworks with losing JSX and being more understandable for fullstack engineers in smaller teams who might not know React. They have now made a direct competition with React though and badly implemented a lot of apis (simple things like grepability and codemods are lacking). They struggled with this release for a year and now they are still behind where React is focusing on server components, concurrent rendering and the tools we need for WASM to be implemented in the most performant ways now ie11 is officially leaving support this year. Some have said it here too that the whole ecosystem felt beta and now the largely community based ecosystem is either leading to vue3-* packages which just make an upgrade to Vue 3 a full on migration.
- Blackstone4 5y agoYou are doing a full migration to React because of the update from Vue2 to Vue3? I read the Vue3 docs for the key differences and it looks a lot easier to migrate to Vue3 than React....
- sidhuko 5y agoThe question is what next? Our team had already started migration from vuex to solely using Apollo. Apollo then changed their own standards like depreciating local resolvers. Vue 3 release seemed to change regularly from will it or won't it support ie11 and various other additional packages. It is fairly easy to build React-in-Vue code to do a similar migration but the "experts" in Vue often just live in the short term without really committing too a level of support that an enterprise team needs with 20-30 developers. With React I'm sure any major changes will be a phased thing so I can continue to upgrade through the major releases for new features while updating code to new patterns. There is usually codemods to automate any changes because the coding patterns are highly developed to be testable and consistent to change. Similar support exists around the community of packages like Redux. Vue is stretched across multiple projects like state management, build tooling and DX while genuinely being behind the curve in best practices like testing and static code analysis. A Vue 2 to 3 migration is really a complete overhaul of every component to allow you to upgrade to v3. That is a huge liability of an inexperienced team who I expect to make similar mistakes with their community.
- VUETHEBROKENSYS 5y agoAt this point in time we can all learn that Vue was broken by incompatible changes. The horror you see in the whole ecosystem was predictable, but Evan did not understand how destructive his strategy is. It is really clear that the changes in Vue 3 where implemented in a way where it is simply too much of a hassle to migrate for too many people - most of the ecosystem still does not work with Vue 3. A new version breaking old code can be bulldozered into the world only by real godzilla projects like Python - and even there it triggers years of discussion and upgrade-resistence and lots of dead projects. As a programmer of a small JS library you can learn from the fail of Evan: breaking backward compatiility is breaking your ecosystem - the most important resource you have. Disrespecting this resource will kill you. The Vue project nowadays can be seen as dead - many projects got that "Angular-Burn" and will never upgrade, but switch to something else. People still hanging on are the slow crowd that get things too late - we have many of these, but there is no creativity in these people, nothing to expect, just copypasta followers. Hopefully other projects finally learn from this sad example. Please do not break your ecosystem. Thanks.
- pjmlp 5y agoI guess I wasn't wrong to keep using Angular, all alternatives eventually become as complex, with lots of little libraries to keep track of.
- adreamingsoul 5y agoAngularJS or Angular? I was a hold out with Angular 1.x. As a library, it was great. My team understood the strengths and weaknesses, and we utilised almost all of the features that it provided. The >2.x releases didn’t provide much value for us, and didn’t solve any problems that we had. So the motivation to migrate and refactor was low. I still think Angular 1.x is a decent library, and have often contemplated contributing fixes/security to a fork.
- pjmlp 5y agoAngular, if I wanted to say AngularJS, I would have written as such. However, if you see other posts from me, you would also notice that I am largely involved in projects that are quite strong in Java and .NET stacks with SSR. So even Angular isn't there in every project.
- deleted 5y ago[deleted]
- darkhorse13 5y agoAgreed. I really liked AngularJS in spite of all its shortcomings. To me, it felt a lot more traditional I guess, and coming from Python/Django, I really enjoyed that. React on that other hand, I can't seem to gel with it at all.
- 5350-uiop-1130 5y agoah the ever changing world of web dev. just when you think you've learnt something, the rug gets pulled out from under you.
- Bigpet 5y agoChose Vue3 on whim for a weekend project last week. I was well into the first couple pages until I realized that some of the documentation seemed to have a completely different approach. Then I realized the difference between the Options API and Composition API. That an pairing it with Typescript made things really unecessarily hard for learning. All the TS documentation assumed you already mastered the old and new APIs. Really glad they have the Options/Composition toggle in their new docs now. Looks like I chose exactly the wrong time to look into it.