Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vue 3.0 Updates [slides]

docs.google.com

Post reply on HN
Print view View original

51–60 of 126 posts

Re: Vue 3.0 Updates [slides]

#51

Post by gbuk2013 »

TekMol wrote: post #16

My feeling is that most people who use Vue or React only need a template engine. Typical use case: You have an array of objects and a template how each object should look like. So you do... {{ user.name }} let userList = new Vue({ el : '#users', data: { users: users } }) ...to make Vue render the list of objects. This is the only thing I ever use these frameworks for. Everything else I think I can implement in a bett…

One should use what is necessary and no more. If server side templates work for you - great.

My rule of thumb: if I need to do more then a trivial amount of DOM manipulation then I will use a framework, because otherwise I will end up writing my own anyway (which I can easily do) which wastes development time.

For projects with several developers a framework can help maintain common coding style and reduce ramp up time for new hires.

Also, good frameworks come with nice tooling that make for more productive development. For example, Vue + Vuex and the Vue browser plugin are great for inspecting the state and observing state transitions.

An example of my use case: I have a non-SPA app that receives various data via Websocket and the view is immediately updated. Several components take this same data and render it in different ways. Vue is excellent for this. I still use templating on the server side for the basic page structure.

Re: Vue 3.0 Updates [slides]

#52

Post by pdkl95 »

> ... implementation re-written from the ground up

Rewriting a big project from scratch is often used as something to brag about: "Look at all the hard work we accomplished!". Except in software what matters is correctness and efficiency, not the age or the code or the size fo the rewrite. Rewriting "from the ground up" is throwing away years of bugfixes[1].

Maybe this new version is fine; I'm only suggesting that big re-implementations should be seen as an unknown risks, and that "carefully refactored problematic areas of the code" is something worth bragging about on a slide.

[1] https://www.joelonsoftware.com/2000/04/06/things-you-should-...

Re: Vue 3.0 Updates [slides]

#53

Post by resource0x »

pdkl95 wrote: post #52

> ... implementation re-written from the ground up Rewriting a big project from scratch is often used as something to brag about: "Look at all the hard work we accomplished!". Except in software what matters is correctness and efficiency, not the age or the code or the size fo the rewrite. Rewriting "from the ground up" is throwing away years of bugfixes[1]. Maybe this new version is fine; I'm only suggesting that bi…

> Rewriting a big project from scratch is often used as something to brag about

Not necessarily. Sometimes it means "our old code was such a mess no one could make any sense of it" :)

Re: Vue 3.0 Updates [slides]

#54

Post by bpicolo »

pdkl95 wrote: post #52

> ... implementation re-written from the ground up Rewriting a big project from scratch is often used as something to brag about: "Look at all the hard work we accomplished!". Except in software what matters is correctness and efficiency, not the age or the code or the size fo the rewrite. Rewriting "from the ground up" is throwing away years of bugfixes[1]. Maybe this new version is fine; I'm only suggesting that bi…

When your project is such a size that a single person can keep it all more or less in their head (in this case, Evan), clean slate rewrites end up being fairly efficient. It's a much different case than 20->200->2000 devs scale applications. It's vastly more easy to develop something from scratch if you'd put a lot of thought into it over time

Re: Vue 3.0 Updates [slides]

#55

Post by pier25 »

Vue 3 is a massive new update:

- TypeScript

- Double the performance

- Half the size and memory consumption

- New reactive system that supports classes a la MobX

- Class based components

I've been using Vue for a couple of years and I'm very excited about this new release.

Re: Vue 3.0 Updates [slides]

#56

Post by bloopernova »

TekMol wrote: post #38
dpau wrote: post #33

Earlier quoted context omitted.

If you're just rendering HTML, you might as well do it on the server with your choice of language/framework. The power of Vue and other Javascript frameworks is in their reactivity and the ability to create extremely powerful interfaces.

I only use Vue when I need to alter the data clientside before it gets rendered. For example mark some of the users in the list as friends depending on which friends the user has stored in localStorage. If the data is ready to render while still on the sever, I do so.

I'm DevOps, with 20+ years background in Ops. So the Dev side of things often fascinates and confuses me.

Thank you for clearly talking about why you'd use Vue and when you wouldn't. It's this sort of experience-based knowledge that I often lack.

I'm currently writing basic (very basic!) node stuff intended to further my understanding of Kubernetes: accessing a database, talking to a redis instance, etc etc. It can be bewildering trying to navigate the "oh-so-easy" basic examples of different frameworks and compare their different features.

Hm, that sounds like I'm asking for help, which I'm not - I just want to give an example of why your comments were so helpful to me!

Re: Vue 3.0 Updates [slides]

#57

Post by douglaswlance »

pdkl95 wrote: post #52

> ... implementation re-written from the ground up Rewriting a big project from scratch is often used as something to brag about: "Look at all the hard work we accomplished!". Except in software what matters is correctness and efficiency, not the age or the code or the size fo the rewrite. Rewriting "from the ground up" is throwing away years of bugfixes[1]. Maybe this new version is fine; I'm only suggesting that bi…

Vue itself is less than 10,000 lines. It's not a huge project.

Re: Vue 3.0 Updates [slides]

#58

Post by goliatone »

whyevenbother wrote: post #30
akhilcacharya wrote: post #19

Earlier quoted context omitted.

Using the createElement structure is more annoying than just doing a es6 template string in Vue.

Moving the goalpost. I'm only pointing the fact that it is possible, and saying it is impossible is false. Personally, I don't find the function-call format that "annoying", and I think it presents some advantages neither JSX nor template strings have, along with some disadvantages (it's more verbose, like you pointed out).

And I think GP was saying even if possible it seems rather irrelevant. You could use react without JSX but most likely you will not because you would be throwing away the good things about react. Technically you can eat soup using a fork, but you won’t because...

Re: Vue 3.0 Updates [slides]

#59

Post by bloopernova »

beaconstudios wrote: post #21
TekMol wrote: post #16

My feeling is that most people who use Vue or React only need a template engine. Typical use case: You have an array of objects and a template how each object should look like. So you do... {{ user.name }} let userList = new Vue({ el : '#users', data: { users: users } }) ...to make Vue render the list of objects. This is the only thing I ever use these frameworks for. Everything else I think I can implement in a bett…

as a React developer, SPAs in general are overused. Most LOB apps could (and should) still be written in a backend templated language. SPAs should be reserved for applications (or even individual components) with advanced interactive features, ie a proper web app.

Just to confirm: SPA = Single Page Application. What does LOB mean?

Re: Vue 3.0 Updates [slides]

#60

Post by beaconstudios »

bloopernova wrote: post #59
beaconstudios wrote: post #21

Earlier quoted context omitted.

as a React developer, SPAs in general are overused. Most LOB apps could (and should) still be written in a backend templated language. SPAs should be reserved for applications (or even individual components) with advanced interactive features, ie a proper web app.

Just to confirm: SPA = Single Page Application. What does LOB mean?

line of business. It's basic internal apps most software devs are working on. Usually 90%+ CRUD forms and tables.
Post reply on HN