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

211–220 of 308 posts

Re: Vue.js 3

#211

Post by punnerud »

brlewis wrote: post #190
RNCTX wrote: post #126

Vue is the only one of the most popular 3 frameworks that can easily be used on a minimal basis to sort of "spruce up" old applications by selectively adding it here and there in the templates. Seems like they should try more marketing and community outreach toward that end. Gradual adoption is a feature / selling point not many web development frameworks can claim.

> Vue is the only one of the most popular 3 frameworks that can I don't know if you intended it this way, but the start of this comment makes it automatically flamebait. Discussion around release announcements can quickly turn into a flame war. Please use caution.

And a flame war, aka lot of comments compared to votes on HN, result in less time on the front page. So there is not the biggest benefit to oversell.

Re: Vue.js 3

#212

Post by brylie »

I've been confused by some of Evan's presentations about performance gains and other statistics. For example, the release notes say

> updates (up to 133% faster)

How can something be > 100% faster?

Re: Vue.js 3

#213

Post by Roboprog »

brylie wrote: post #212

I've been confused by some of Evan's presentations about performance gains and other statistics. For example, the release notes say > updates (up to 133% faster) How can something be > 100% faster?

By doing twice as much in the same time, I guess.

Re: Vue.js 3

#214

Post by wenc »

brylie wrote: post #212

I've been confused by some of Evan's presentations about performance gains and other statistics. For example, the release notes say > updates (up to 133% faster) How can something be > 100% faster?

If you take 100% faster to mean 2x faster (takes 1/2 the orig time), 200% faster to mean 3x faster (takes 1/3 the orig time)...

Then 133% faster means 2.33x faster (takes 1 / 2.33 = 0.42 the orig time).

Re: Vue.js 3

#215

Post by wmf »

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?

Market growth can cover a lot. Even if, say, Svelte gets bigger than Vue in the future, Vue could still be bigger than it is today.

Re: Vue.js 3

#216

Post by SPascareli13 »

swyx wrote: post #186
RNCTX wrote: post #126

Vue is the only one of the most popular 3 frameworks that can easily be used on a minimal basis to sort of "spruce up" old applications by selectively adding it here and there in the templates. Seems like they should try more marketing and community outreach toward that end. Gradual adoption is a feature / selling point not many web development frameworks can claim.

i'm afraid this is pretty much plain wrong. react and svelte also support incremental adoption, and i dont know angular but i'd hazard there's a way to do it too if you bothered to ask angular devs. what you're responding to is marketing , which Vue has done an effective job of. thats fine, but it is unfair of you to conclude "Gradual adoption is a feature / selling point not many web development frameworks can claim…

I can tell you that not only he is right, but I've used Vue for exactly that purpose before and works like a charm.

You can go pretty far using Vue with a tag before you start needing build tooling.

Re: Vue.js 3

#217

Post by lhorie »

jhall1468 wrote: post #210
lhorie wrote: post #200

Earlier quoted context omitted.

React is a quite bit more all-in than Vue though. For example, an old app I'm aware of has HTML generated by JSP with its own convoluted maven build process and uses a mix of AngularJS and jQuery to hydrate client-side functionality on top of it. The development workflow is a draconian exercise in acrobatics through remote desktops and VPNs in really old laptops (because "security" and unions). Vue has similar hydrat…

I don't know if "from scratch" is really a fair statement. React accepts HTML in the render function, so the only thing you'd need to do is modify the variables to match JSX's variable syntax, which is exactly what you'd have to do with Vue. I think it's all pretty much the same deal. You might argue Vue's template syntax is closer to HTML than JSX is, but that doesn't really feel like the major issue when slowly ref…

I'm not talking syntax. I'm saying that vue can be added on top of a third party DOM that may have server-rendered data embedded in it. You cannot hydrate React on top of dynamic HTML that was generated with JSP/PHP/.NET/etc unless you a) give up JSX (a big departure from idiomatic React) and b) interpolate server variables into your JS (a no-no in pretty much every non-SPA framework)

For example, take a rails app, then do the equivalent of $('#foo').toggle() based on some condition. In React, AFAIK you can't unless React knows what the markup being toggled is somehow. Vue can do it without knowing anything about the markup inside, and more importantly, the code will look idiomatic.

Re: Vue.js 3

#218

Post by holtalanm »

swyx wrote: post #186
RNCTX wrote: post #126

Vue is the only one of the most popular 3 frameworks that can easily be used on a minimal basis to sort of "spruce up" old applications by selectively adding it here and there in the templates. Seems like they should try more marketing and community outreach toward that end. Gradual adoption is a feature / selling point not many web development frameworks can claim.

i'm afraid this is pretty much plain wrong. react and svelte also support incremental adoption, and i dont know angular but i'd hazard there's a way to do it too if you bothered to ask angular devs. what you're responding to is marketing , which Vue has done an effective job of. thats fine, but it is unfair of you to conclude "Gradual adoption is a feature / selling point not many web development frameworks can claim…

as someone who has used both Vue and React in a _very_ legacy system, I can say unequivocally that Vue was massively easier to integrate into our system than React was.

Re: Vue.js 3

#219

Post by lokethien »

erokar wrote: post #115
LocalPCGuy wrote: post #109

Earlier quoted context omitted.

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 cap…

Depends where you live and work I suppose. I used to work in a consultancy firm in Norway that was all in on Angular two-three years ago. Angular has been very popular in enterprise here. But Twitter and Reddit reach enterprise too in the end. The consultancy firm has now switched more or less entirely over to React because Angular is so out of vogue.

Similar story in the old company I worked for. Though I have experienced that there are a few companies that are happy with Angular and see no reason to switch.

Re: Vue.js 3

#220

Post by JMTQp8lwXL »

sdfhbdf wrote: post #127
mattlondon wrote: post #122

Earlier quoted context omitted.

Angular is massive - MASSIVE - within large orgs you will have heard of but which I cannot name for obvious reasons. The twitterati and hobbyist crowd seem to love react, but anecdotally I've yet to see it used seriously at a BigCo, but Ng+TS is everywhere.

Your comment seems to present anecdotal evidence as facts about $framework's popularity. I think that's misleading. I'm wondering if there's a scraper out there crawling Alexa TOP 1xxx pages for use of specific libraries, frameworks? Maybe that would present a more accurate picture about this. Also it's often misleading since in any company with more than a few employees there seems to be more than one team of develo…

A lot of the web isn't publicly accessible. And most .com marketing sites are built on a much different tech stack than the actual product. Example: landing page is Wordpress, actual site is a SPA (be it React/Angular/Vue etc).
Post reply on HN