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

Vue.js 3

github.com

Post reply on HN
Print view View original

101–110 of 308 posts

Re: Vue.js 3

#101

Post by wenc »

mushufasa wrote: post #68
didip wrote: post #63

I am impressed with the amount of energy Evan is pouring in this open source project. I am curious if he ever experience boredom working on Vue. I am also curious if Patreon based income is sustainable for the long run. What if there's another new sexy JS framework in the future?

> What if there's another new sexy JS framework in the future? That's how a market works. It's a strong incentive to keep Vue sexy.

The closest thing I can see to a contender is Svelte.

I'd be unlikely to start any new project on Angular. React remains dominant and would be a viable option, except Vue feels more lightweight and approachable. I'm sticking with Vue for now.

Re: Vue.js 3

#102

Post by pletnes »

huseyinkeles wrote: post #15
tyingq wrote: post #11

Earlier quoted context omitted.

It's definitely not how to show that, but if you follow their link ( https://docs.google.com/spreadsheets/d/1VJFx-kQ4KjJmnpDXIEai... ), you'll see the numbers. The math is like, if it did use 100mb, and now it uses 25mb, that's 300% less, because 25mb is the "100%", and you reduced by that amount 3 times. Odd.

Is this the lingo that statisticians/mathematicians use? I’d just say 75% drop for 100mb to 25mb.

No, it’s plain wrong. You could say «vue 2 uses 120% more memory than vue3», but vice versa is thus a different percentage (yes, 75%).

Re: Vue.js 3

#103

Post by blntechie »

erokar wrote: post #98
selfmodruntime wrote: post #75

Earlier quoted context omitted.

The market also isn't as volatile as people make it out to be. The top most used js frameworks (React, Angular and Vue) have been in the top spots for 5 to 7 years now. I guess the market might as well be settled. Of course there are some new comers every year, but they don't enjoy a large market share. Hell, I've not even seen VueJS used once in any serious project in the industry. React and Angular are here to stay…

Angular seems to be dying. Svelte is an interesting contender. I think it will be React's main competitor given a year or two.

Angular is huge inside big enterprises. Much more popular than React.

Svelte is very cool though.

Re: Vue.js 3

#104

Post by Exuma »

TekMol wrote: post #97
Exuma wrote: post #49

Earlier quoted context omitted.

It's almost a necessity for complicated apps. Right now I'm building an app which involves a reporting screen with all the following features on a single page: - 10+ breakdowns for report - 10+ filters for report - Each filter has an include/exclude dropdown list which then has multiple features within even a single filter (so some filters are EQUALS/NOT EQUALS) others are INCLUDES/DOESNT INCLUDE/EMPTY/NOT EMPTY and…

Nothing you describe is easier solved with Vue then with a templating engine. You can have a "DropdownMenu" template, feed it the data (which you call "state") and update the according element on screen just fine.

What do you mean by 'templating engine'. Give me a specific example. Templating engines to me are like handlebars... do you have a sample code example?

Re: Vue.js 3

#105

Post by gavinray »

mthoms wrote: post #82
gavinray wrote: post #40

Earlier quoted context omitted.

Kind of -- reactive() lets you declare multiple values at once, and you can read the property directly. ref() is for single values, and to get at the actual VALUE, you need to use "myRef.value" const state = reactive({ msg: "hello", count: 1 }) state.msg // "hello" const msg = ref("hello") msg.value // "hello" Though when you use ref()'s in templates, it will bind to .value for you.

I find myself using `const state = reactive({...})` exclusively now. It's just way simpler (read:less mental overhead). But, I've only been using the composition API for a short while now. Do experienced Vue devs actually use both regularly?

Personally, I rarely use refs. I think they have more use when creating general-purpose libraries for Vue.

You can also just call "toRefs()" on a "reactive()" object though.

Refs are also useful if you want to destructure a reactive object without breaking the reactivity, scroll down just below this:

https://composition-api.vuejs.org/api.html#torefs

Re: Vue.js 3

#106

Post by wishinghand »

didip wrote: post #63

I am impressed with the amount of energy Evan is pouring in this open source project. I am curious if he ever experience boredom working on Vue. I am also curious if Patreon based income is sustainable for the long run. What if there's another new sexy JS framework in the future?

> I am curious if he ever experience boredom working on Vue.

I was curious about this too when Vue 3 overshot its release estimate and then he started working on Vite, which is a build tool.

Re: Vue.js 3

#107

Post by jtdev »

selfmodruntime wrote: post #75
mushufasa wrote: post #68

Earlier quoted context omitted.

> What if there's another new sexy JS framework in the future? That's how a market works. It's a strong incentive to keep Vue sexy.

The market also isn't as volatile as people make it out to be. The top most used js frameworks (React, Angular and Vue) have been in the top spots for 5 to 7 years now. I guess the market might as well be settled. Of course there are some new comers every year, but they don't enjoy a large market share. Hell, I've not even seen VueJS used once in any serious project in the industry. React and Angular are here to stay…

I’ve deployed a number of applications using Ember’s (Octane) and will continue to use that over React, Angular, and Vue for as long as these other frameworks continue to prioritize fp zealotry over getting shut done.

Re: Vue.js 3

#108

Post by save_ferris »

selfmodruntime wrote: post #75
mushufasa wrote: post #68

Earlier quoted context omitted.

> What if there's another new sexy JS framework in the future? That's how a market works. It's a strong incentive to keep Vue sexy.

The market also isn't as volatile as people make it out to be. The top most used js frameworks (React, Angular and Vue) have been in the top spots for 5 to 7 years now. I guess the market might as well be settled. Of course there are some new comers every year, but they don't enjoy a large market share. Hell, I've not even seen VueJS used once in any serious project in the industry. React and Angular are here to stay…

I agree that there will be a need for react/angular talent for many years to come. That said, I think engineering orgs are picking up on the fact that rolling web apps this way introduces lots of complexity and requires lots of resources to maintain and extend. I really don't want to think about regularly maintaining a 10-year-old redux-backed react app down the road.

Whether react/angular/vue are able to continue improving enough to justify staying within that world remains to be seen. It's very early days for some of the new frameworks out there, but with web assembly on the horizon, companies will again be motivated to modernize, however that looks.

Re: Vue.js 3

#109

Post by LocalPCGuy »

erokar wrote: post #98
selfmodruntime wrote: post #75

Earlier quoted context omitted.

The market also isn't as volatile as people make it out to be. The top most used js frameworks (React, Angular and Vue) have been in the top spots for 5 to 7 years now. I guess the market might as well be settled. Of course there are some new comers every year, but they don't enjoy a large market share. Hell, I've not even seen VueJS used once in any serious project in the industry. React and Angular are here to stay…

Angular seems to be dying. Svelte is an interesting contender. I think it will be React's main competitor given a year or two.

This is a popular opinion particularly if all someone pays attention to is Twitter and Reddit but I'd argue it is a wrong opinion.

Angular is alive and well, and being used/adopted every day for projects no one hears about. It isn't the "sexy" choice, but it is the one a lot of companies make.

And if you're gonna point to opinion polls, and all kinds of respect to those who put them out, but they have a hard time capturing Angular usage due to selection bias.

Re: Vue.js 3

#110

Post by Exuma »

TekMol wrote: post #92
selfmodruntime wrote: post #69

Earlier quoted context omitted.

It's great you applied your vanilla JS skills to his totally metaphorical example. I still don't get why it's okay for every other programming language to use the STL or huge dependencies, but doing so with javascript is frowned upon for some people. You wouldn't write a JSON parser yourself in CPP, you'd install something from conan or use the STL or boost for that. Why is it so bad to do the same with js?

The browser does supply a huge number of APIs. To set one of the Minesweeper tiles to bomb, you could do: tiles[x][y].className='bomb'; And you are done. The rendering will nicely take place according to what you defined in the CSS.

What are you talking about? You're just talking about simple class manipulation which has nothing to do with actual reactivity, especially 2-way data binding.

How would you support that with your "templating engines" you keep mentioning, which to me doesn't mean anything at all, in my understanding of what a templating engine is like handlebars.

Post reply on HN