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

231–240 of 308 posts

Re: Vue.js 3

#231

Post by k__ »

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.

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

Re: Vue.js 3

#232

Post by runarberg »

barrkel wrote: post #224
yandie wrote: post #151

Earlier quoted context omitted.

I find it amusing that you are allowed to run arbitrary Javascript but can't run NodeJS on your machine. Sometimes corporate security can be a theatre.

I wish we couldn't run NodeJS, then the front end devs wouldn't run this monstrosity that takes ages to start, downloads GBs of dependencies, consumes 12 cores for minutes at a time, etc. I exaggerate, but only slightly.

I find this attitude towards front-end developers unamuzing. If you have a beef with subset of developers in your workplace that happen to to work on the front-end, you should not take your frustration or generalize their behavior over an entire industry.

Re: Vue.js 3

#233

Post by aethr »

diminish wrote: post #24
lykahb wrote: post #4

I am impressed how they redesigned both internal architecture and a public API while keeping the users happy. Many well written projects fall into the trap of being a great fit for the contemporary practices but become less relevant over time as the ecosystem changes. Well done, Vue!

curious how easy it will be to move from vue 2 to vue 3

I am working on this right now on a medium-sized project, and it's deceptively more work than we anticipated. While Vue's component API itself is remaining mostly backwards compatible with Vue 2, most of the "core" supporting libraries have changed their APIs: Vuex, VueRouter and vue-test-utils in particular.

After the package update and some very basic find/replace across our codebase, about half of our 600+ tests had to be significantly updated. If your tests regularly mock a Vuex store or a router, be prepared to be making a lot of updates.

If you're using some of the features being removed (filters, $on/$off/$once, etc) or make heavy use of custom plugins, it's not going to be painless.

Having said that, I love the direction the new API is heading and 95% of the changes we have to make are for the better in the end, so it feels worth it.

Re: Vue.js 3

#234

Post by andrewflnr »

SPascareli13 wrote: post #216
swyx wrote: post #186

Earlier quoted context omitted.

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.

That's not where they were wrong.

Re: Vue.js 3

#235

Post by RNCTX »

lhorie wrote: post #217
jhall1468 wrote: post #210

Earlier quoted context omitted.

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, t…

> and more importantly, the code will look idiomatic.

That's the kicker.

Whether a thing is possible or not is a far cry from whether it's a good idea. And when you consider what someone who opens up the code 5-7 years later without any frame of reference to start from will think (which can just as well include the original author if the original author has moved on to other things), familiar syntax goes a long way.

Re: Vue.js 3

#236

Post by andrewflnr »

dane-pgp wrote: post #194
umvi wrote: post #130

So it looks like Vue releases are all named after anime? For anyone curious, here's the full list: https://en.wikipedia.org/wiki/Vue.js#Versions

Is that a JoJo reference?

It's my understanding that anything can be a JoJo reference if you want it to be.

Re: Vue.js 3

#237

Post by billisonline »

mattlondon wrote: post #122
erokar wrote: post #98

Earlier quoted context omitted.

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 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?

Re: Vue.js 3

#238

Post by RNCTX »

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.

The "easily" in that sentence is an important word...

Re: Vue.js 3

#239

Post by 3131s »

cjohnson318 wrote: post #47
TekMol wrote: post #38

I still don't see a reason why one would use Vue or React. I agree that templating of data is something you should use a library for. But there are great templating libraries. Handlebars for example. Can someone give a short example of code that would be more elegant using Vue then just a simple template engine?

One example is building an application like minesweeper. Would you really want to tackle that with jQuery and templating engine? I'd rather break everything into components, have them talk to each other through a state manger like vuex or redux, and only phone home to my API for important things, like the final game score.

I made a minesweeper clone in JS and CSS, it's not as hard as you'd think and just a few hundred lines of code. I still want to attempt a multiplayer minesweeper, which might benefit more from something like Vue.

A dashboard is usually for me the primary use case for one of these reactive frameworks.

Re: Vue.js 3

#240

Post by lhorie »

k__ wrote: post #231
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.

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 in v-clicks on existing HTML.

You can certainly adopt react "incrementally", in the sense that you can implement an entire new self-contained feature and plop it into an existing app if it already uses REST APIs, but react is decidedly not as trivial to sprinkle into a non-SPA where data comes mixed with HTML rendered on the server.

Post reply on HN