Live data from Hacker News

Vue.js 3

github.com

261–270 of 308 posts

Re: Vue.js 3

#261
post #260

One thing I'm really excited about with this version is Vite (the snowpack type version of Vue that doesn't require webpack). It should make development so much easier.

As someone who includes we pack in my build chain in order to use vue but doesn't truly understand it and has never used Cute, can you explain the advantages?

This is straight out of the horses mouth:

- Lightning-fast cold server start - Instant hot module replacement (HMR) - True on-demand compilation

This part should be of particular interest to you:

https://github.com/vitejs/vite#how-is-this-different-from-vu...

Re: Vue.js 3

#262
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 wouldn't say this is the main selling point of Vue. For me Vue is superior exactly in the opposite scenario: when one has to build a complex SPA. State management, routing, and the like is all well integrated in the Vue ecosystem whereas, for example, in the React world it's a pita. I like React's simplicity, but I cannot deal with any of its complementary libraries for state management.

Re: Vue.js 3

#263

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.

"I've yet to see [React] used seriously at a BigCo" you realize Facebook a) sponsors its development and b) just rewrote their core product in it?

c) I've never worked at Facebook so I've not seen their work and obviously I don't use Facebook.

Re: Vue.js 3

#264
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.

You may want to look at projects like preact-habitat, stimulus, and web components (a la polymer). Vue isn't the only game in town for this functionality.

Re: Vue.js 3

#265

Earlier quoted context omitted.

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.

That's not where they were wrong.

Look, I've used both Vue and React for this purpose and Vue is just easier to integrate. React can do it too, but Vue places an emphasis on it and it shows.

Re: Vue.js 3

#266
post #240
post #231

Earlier quoted context omitted.

As far as I know, what you are talking about was the main reason React was created in the first place. All this FUD spread by the Vue fans is getting ridiculous...

Not trying to hurt any feelings here, but as far as I can see as an unbiased person who's looked at far too many frameworks for their own good, the FUD is coming from the React fans. I'm seeing a bunch of commenters getting defensive and saying "well technically" while conveniently ignoring the difference in effort required to do islands in each framework. You can't say dropping JSX is at all comparable to plopping i…

Saying React can do it is a fact. So React devs are not spreading any FUD whatsoever.

Saying React can't do it, to paraphrase you, because "technically it's harder than with Vue" is like saying nobody can drive a stick shift because you have to shift gears manually.

Yes, you have to do it manually, no it doesn't make the car undrivable.

That's what I call FUD.

Re: Vue.js 3

#267
post #266
post #240

Earlier quoted context omitted.

Not trying to hurt any feelings here, but as far as I can see as an unbiased person who's looked at far too many frameworks for their own good, the FUD is coming from the React fans. I'm seeing a bunch of commenters getting defensive and saying "well technically" while conveniently ignoring the difference in effort required to do islands in each framework. You can't say dropping JSX is at all comparable to plopping i…

Saying React can do it is a fact. So React devs are not spreading any FUD whatsoever. Saying React can't do it, to paraphrase you, because "technically it's harder than with Vue" is like saying nobody can drive a stick shift because you have to shift gears manually. Yes, you have to do it manually, no it doesn't make the car undrivable. That's what I call FUD.

The problem is that somebody gave a compliment to vue, and immediately a bunch of react people came with their "well actually"

React wasn't even mentioned, don't know why so defensive, who cares

Re: Vue.js 3

#268
post #266

Earlier quoted context omitted.

Saying React can do it is a fact. So React devs are not spreading any FUD whatsoever. Saying React can't do it, to paraphrase you, because "technically it's harder than with Vue" is like saying nobody can drive a stick shift because you have to shift gears manually. Yes, you have to do it manually, no it doesn't make the car undrivable. That's what I call FUD.

The problem is that somebody gave a compliment to vue, and immediately a bunch of react people came with their "well actually" React wasn't even mentioned, don't know why so defensive, who cares

I very much doubt the original comment mentioning "the most popular 3 frameworks" didn't have React in mind as one of those, even if they didn't spell it out, so that complaint IMHO makes little sense.

Re: Vue.js 3

#269
post #266
post #240

Earlier quoted context omitted.

Not trying to hurt any feelings here, but as far as I can see as an unbiased person who's looked at far too many frameworks for their own good, the FUD is coming from the React fans. I'm seeing a bunch of commenters getting defensive and saying "well technically" while conveniently ignoring the difference in effort required to do islands in each framework. You can't say dropping JSX is at all comparable to plopping i…

Saying React can do it is a fact. So React devs are not spreading any FUD whatsoever. Saying React can't do it, to paraphrase you, because "technically it's harder than with Vue" is like saying nobody can drive a stick shift because you have to shift gears manually. Yes, you have to do it manually, no it doesn't make the car undrivable. That's what I call FUD.

I gave some examples downthread where react pretty much falls apart. I'm sure you "technically" could make it work by dropping down to vanilla and cloning nodes or refactoring backend code or whatever, but at that point it's not merely "technically a bit harder", it's a pretty huge stretch.

The car gear analogy is again downplaying magnitude. The examples I gave are not a comparison between auto vs manual, it's more like auto vs getting a different license type to drive a 18 wheeler and having to learn how to turn, back out, park, go under bridges and where you're allowed to drive and not all over again. Yes, it's technically doable, no it's anywhere near similar amounts of effort as just learning stick.

To clarify, again, just because it feels like react vs vue is akin to manual vs auto when you're in a codebase that is amenable to being refactored into react, it doesn't change the fact that there are types of codebases (non-SPAs without HTTP API layers) where migrating to react is a significantly larger investment than vue. That was what the OP was saying.

Re: Vue.js 3

#270
post #178
post #172

Earlier quoted context omitted.

Modern React uses JSX which is then transformed at build time into function calls. You can write those function calls yourself, but it would be a tremendous PITA.

In this case, you could use `htm`: https://github.com/developit/htm#usage

That's cool- but unless you're targeting greenfield browsers only you aren't going to use the syntax in that documentation without a build step or using the babel transpiler directly in the browser which, while cool from a POC standpoint, isn't a good solution. At that point you might as well just add build tools and use JSX or whatever the framework you're trying to use intended or otherwise is well documented.
Post reply on HN