What's the point of that comment, on a post about Vue.js, if it's not just being purposefully controversial?
If anything, this makes Vue.js even more similar to React's functional API, so if it's V2's API you don't like, this post should have the opposite effect.
It's a second API and the "old" one isn't going away any time soon. Everyone's free to ignore it altogether and keep working like before. It IS a major selling point.
Java developer, passionate about sci-fi lit, facial hair and a good, hot chicken broth. Totoro is my daily inspiration. You will never catch me wearing sandals.
oh com'on!! why?? ☹️ why can't we have a framework that uses language keywords for what they meant for?? export for binding fields to a template? what's the semantic here? export is meant for exporting "things" from a module, is template a JS module?
Svelte is just terrible and horrible on this side, and Vue 2 was just perfect (maybe it needed to simplify some things), but in this way is getting closer to what Angular 2+ is for AngularJS: bloody mess. 😕 quite disappointed
Java developer, passionate about sci-fi lit, facial hair and a good, hot chicken broth. Totoro is my daily inspiration. You will never catch me wearing sandals.
I know but it's not what I meant, such kind of dirty tricks do not improve in any way the development consistency and conventions. And I don't get why some JS framework development deliberately ignore this from the beginning.
I know I can be a little bit dramatic, but a RFC like this should be blasted without any discussion.
It’s not just an RFC per day, it rather a facade from past experience. And just like React functional components, the composition API will be the standard.
export for binding fields to a template? what's the semantic here? export is meant for exporting "things" from a module, is template a JS module?
export isn't binding fields to the template, it's creating a JS object which Vue builds into a "reactive" object when you run the build command to compile the code. This is why we include export default or module.exports when we write a single file component in Vue 2.X.
Java developer, passionate about sci-fi lit, facial hair and a good, hot chicken broth. Totoro is my daily inspiration. You will never catch me wearing sandals.
I'm a full-stack Software Engineer and Architect. I specialise in front-end niceness, but my daily tasks are mostly about making server less work well and scale within our suit of micro services!
The new composition API is actually more difficult to understand. Vue2 was very declarative with the options API. I’m not sure what advantages this brings? It’s not like you have to include all options...
Moreover, this seems like overkill to fix the mixin problem? Sounds like they just got hook envy....
This post was more to show the new syntax, not the benefits of the composition API. Hence, my example is actually really bad from that stand point. Composition API shines once you have (with options API) related logic spread across different options (data, computed, methods, mounted, destroy, etc.). Composition API let's you group this logic together. It's not going to be an all-in replacement for Vue 2's options API. I can see people continue using it.
Yep most of plugins, build tools, syntaxes, etc will eventually be depreciated. Also documentation and examples will be more difficult to resource if 2.0 isn’t branched into an new project.
That's dramatic. React class based components aren't gone either, a lot of things migrated to them, yet I've still to find a React dev who doesn't know about both functional and class-based.
Yeah I have to agree, I like how with React it doesn't feel like there is "magic" happening behind the scenes, even though there is.
I'm not bashing Vue or Vue users here, it's fine, but after working with it on a massive codebase, I can't use it. These RFCs look like they'll improve some aspects, but I still view Vue as a tool more appropriate for smaller/prototype projects.
I'm a full-stack Software Engineer and Architect. I specialise in front-end niceness, but my daily tasks are mostly about making server less work well and scale within our suit of micro services!
Seriously? I find that interesting. I love React, but I find it’s maintainability goes down very quickly as codebase grows. Vue’s single file components force devs to think very hard about reusability and working on huge code base was a dream
Hey guys, 15-year developer! I code with Vue.js and Python, I love to learn but also love to teach! So I try and write informative tutorials and posts. I am new to blogging and would love any feedback
What's the point of that comment, on a post about Vue.js, if it's not just being purposefully controversial?
If anything, this makes Vue.js even more similar to React's functional API, so if it's V2's API you don't like, this post should have the opposite effect.
From its existing user base and previous vision, it's not a selling point being similar to React.
It's a second API and the "old" one isn't going away any time soon. Everyone's free to ignore it altogether and keep working like before. It IS a major selling point.
Reminds me of Svelte. I love it.
oh com'on!! why?? ☹️ why can't we have a framework that uses language keywords for what they meant for?? export for binding fields to a template? what's the semantic here? export is meant for exporting "things" from a module, is template a JS module?
Svelte is just terrible and horrible on this side, and Vue 2 was just perfect (maybe it needed to simplify some things), but in this way is getting closer to what Angular 2+ is for AngularJS: bloody mess. 😕 quite disappointed
Two things I'd like to point out.
setupwithout the syntax sugar from the RFCI know but it's not what I meant, such kind of dirty tricks do not improve in any way the development consistency and conventions. And I don't get why some JS framework development deliberately ignore this from the beginning.
I know I can be a little bit dramatic, but a RFC like this should be blasted without any discussion.
It’s not just an RFC per day, it rather a facade from past experience. And just like React functional components, the composition API will be the standard.
Hey! Want to help clarify this a bit:
exportisn't binding fields to the template, it's creating a JS object which Vue builds into a "reactive" object when you run thebuildcommand to compile the code. This is why we includeexport defaultormodule.exportswhen we write a single file component in Vue 2.X.So you're actually saying that I'm right, ’export’ is now a special keyword for the build task, not for the language itself. Nice.
I didn't say anything about template tag, at least that one is still complaint.
The new composition API is actually more difficult to understand. Vue2 was very declarative with the options API. I’m not sure what advantages this brings? It’s not like you have to include all options...
Moreover, this seems like overkill to fix the mixin problem? Sounds like they just got hook envy....
This post was more to show the new syntax, not the benefits of the composition API. Hence, my example is actually really bad from that stand point. Composition API shines once you have (with options API) related logic spread across different options (data, computed, methods, mounted, destroy, etc.). Composition API let's you group this logic together. It's not going to be an all-in replacement for Vue 2's options API. I can see people continue using it.
I've been doing Vue since 2 came out. These proposals for 3 are borderline ridiculous. I'll be switching to React or Svelte.
But they are inspired by React and Svelte :/
Or you could just continue using Vue 2.x syntaxing? No one is forcing you....
Yep most of plugins, build tools, syntaxes, etc will eventually be depreciated. Also documentation and examples will be more difficult to resource if 2.0 isn’t branched into an new project.
That's dramatic. React class based components aren't gone either, a lot of things migrated to them, yet I've still to find a React dev who doesn't know about both functional and class-based.
right? and there are nice improvements from a performance perspective in Vue@3 compared to Vue@2
Yeah I have to agree, I like how with React it doesn't feel like there is "magic" happening behind the scenes, even though there is.
I'm not bashing Vue or Vue users here, it's fine, but after working with it on a massive codebase, I can't use it. These RFCs look like they'll improve some aspects, but I still view Vue as a tool more appropriate for smaller/prototype projects.
Seriously? I find that interesting. I love React, but I find it’s maintainability goes down very quickly as codebase grows. Vue’s single file components force devs to think very hard about reusability and working on huge code base was a dream
Could you elaborate that?
Sorry i simply prefer Vue 2 and how we handle the component over v3, we shall see