7 ms·
Vue 3.5 released
- throwup238 2y ago> Tengen Toppa Gurren Lagann I take it back. Buster, bullseye, bookworm, gibbon, fawn, eft, fossa, jellyfish, and numbat are amazing release names. What is this!?
- saikatsg 2y agoJapanese mecha anime television series: https://en.wikipedia.org/wiki/Gurren_Lagann https://en.wikipedia.org/wiki/Gurren_Lagann
- mappu 2y agoThe framework that will pierce the heavens
- pupppet 2y agoDon't believe in yourself, believe in Evan who believes in you.
- ytch 2y agoVue maintainer are using names from manga and anime all the time: https://en.wikipedia.org/wiki/Vue.js#Versions https://en.wikipedia.org/wiki/Vue.js#Versions
- crabmusket 2y agoCan't wait for Planetes to get on that list
- dathinab 2y agonaturally only fictive planets from science fiction looking fantasy stories
- ksec 2y agoI guess you must be a spy from Anti-Spiral. ( Music is already looping in my head..... Who the hell do you think we are !) On a slightly more serious note. I am not sure the release is anywhere close enough to warrant this code name.
- Muromec 2y agoThis is a cultural reference you don’t get. Welcome to the world of every non-native speaker.
- rokkamokka 2y agoI miss the old options API being the primary API :(
- Satam 2y agoYeah, I don't get it. I used Vue because it was straightforward. The options interface was Vue. Now, if it keeps getting more complicated and also has two ways to go about things, and the docs are split into two as well... Why not just go for React that's complicated and more popular?
- Semaphor 2y agoI find the composition API to be clearer and simpler in almost every way. Script setup is amazing. Also proper typescript support without annoying workarounds, that alone would make it worth it.
- sampullman 2y agoI thought the composition API was clunky at first and resisted migrating for a few minor versions, but it's matured nicely. I find it much simpler than the options API, and migration was much easier than I expected. I don't see it as two ways in practice, just the legacy way for old projects (which still has good support), and the newer/better way.
- deleted 2y ago[deleted]
- Woshiwuja 2y ago[flagged]
- michelb 2y agoNot trying to start a framework war, but how do Vue and React compare nowadays? I don't use either, but am interested in learning.
- ramijames 2y agoI work with both and far and away prefer Vue.
- lloydatkinson 2y agoI used to feel this way and then Vue 3 happened.
- ramijames 2y agoVue 3 took some getting used to, but in the end I like the new way of working and its conventions. These days I primarily work in Nuxt and have never felt so productive.
- lloydatkinson 2y agoI migrated back to React
- feverzsj 2y agoReact is more mature, as it has a much larger ecosystem, community, employment opportunities, corporate support.... Vue is simple and delightful when used in small projects. In other words, they are not comparable.
- oefrha 2y agoVue is absolutely a lot more delightful compared to React even in large projects, thanks to fine grained reactivity which React still lacks after all these years (I know people have come up with various bandaids). React wins in ecosystem, i.e. the breadth of available libraries.
- wruza 2y agoVue 2 was the closest thing that I’d really like to use: just my data with methods + declarative ui with bindings. Call me old-fashioned, I still prever model-view relationships separated. Can’t see what’s wrong with having a non-visual model that works on its own and then putting views on top of it to make it accessible to a user. Not only that, I don’t get why I would write model logic in a way that would nail it to a views system. Js objects have observable properties and (with some care) they can even be shared across different subsystems/libraries. What I’d like to see is a UI library that takes my “instanceof Foo” with its value properties, getter properties and methods and observes it. Then I write vue-like html or hyperscript with an assumed root object: import {num_fmt} from “…” import {my_counter} from “…” const view = ( <button onclick={this.reset()}> Reset count: {num_fmt(this.count)} </button> ) ui.mount(some_el, view, my_counter) The my_counter remains free to use elsewhere or to be included into a larger structure. The goal is that ui will notice “.count =” anywhere and schedule an update to dom. Js is absolutely full of features which all these frameworks are trying to reimplement for some reason. There are rough edges that Vue addressed (array obs mostly) and I thought that wow that’s its purpose with some helpers around it. Nice, the next step is to deprecate Options in favor of just js. But it went completely downhill since with sfc and composition and all.
- tecoholic 2y agoCompletely my feelings as well. I have an old desktop app I wrote a few years back in Vue2. The NodeJS version and all related libraries are outdated. But I can’t bring myself to update it to Vue 3. Every time I sit down, I am left wondering why such a rewrite is even necessary. So it’s still chugging along with contributions from others for the old code. When GitHub actions stops building the binary packages, I will have to eventually update I think.
- nsonha 2y agoIt's called Mobx, I use it all the time to not have to touch React's stupid API.
- wruza 2y agoI remember approaching it at least twice, but it didn’t click for me. Should try again, thanks!
- dzonga 2y agothanks Evan + team, one thing I enjoy about Vue is the main API never really changes under you. compared to other frameworks.
- Alifatisk 2y agoWhen will Vapor mode arrive?
- bushwald 2y agoVue is great. I loved the old Options API and was resistant to the new setup/composables way of doing things. But as soon as I tried the new way I loved it. I think it will scale much better as well.
- bricss 2y agoVue + Pinia is the pinnacle of frontend frameworks engineering by far, so far.
- deleted 2y ago[deleted]