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

111–120 of 126 posts

Re: Vue 3.0 Updates [slides]

#111

Post by Zooper »

dmix wrote: post #98
rudolph9 wrote: post #95

Earlier quoted context omitted.

Redux is an independent project from React. You could use redux with Vue. Your other points are valid but detracting from one library because people often use another you don’t care for seems outside the scope of React vs Vue.

Just for the record most people using vue would be using Vuex: https://vuex.vuejs.org Which IMO is simpler to understand as a newbie than Redux. Maybe because it had the luxury of coming after Redux/similar projects and underpinning a simpler parent framework.

Sounds as of 3.0 it became much simpler, as vuex doesn't sound as necessary.

Re: Vue 3.0 Updates [slides]

#114

Post by com2kid »

IgorPartola wrote: post #90
sircastor wrote: post #76

Earlier quoted context omitted.

That's interesting, I started with React, and switched to Vue, and felt Vue was the simpler tool.

Agreed. When evaluating both of them, it looked like React and Vue implement the same concepts, but React did it in ways that made it more complicated than it needed to be. I specifically didn’t like that Redux and it’s docs were too heady for what it really is (it’s just event triggering and handling, why does it have to be so complicated?), and the fact that React didn’t have any official “here’s is how to build a…

Redux is an incredibly simple idea, I have no clue why every explanation of it sucks.

The naming doesn't help.

"Reducers" is just so academic. Maybe a term like "publishers"?

Of course passing data by props instead of receiving a lambda is a bit of a different paradigm already. Takes some getting used to.

Re: Vue 3.0 Updates [slides]

#115

Post by com2kid »

dmix wrote: post #98
rudolph9 wrote: post #95

Earlier quoted context omitted.

Redux is an independent project from React. You could use redux with Vue. Your other points are valid but detracting from one library because people often use another you don’t care for seems outside the scope of React vs Vue.

Just for the record most people using vue would be using Vuex: https://vuex.vuejs.org Which IMO is simpler to understand as a newbie than Redux. Maybe because it had the luxury of coming after Redux/similar projects and underpinning a simpler parent framework.

Redux is at its core super simple.

Action handler gets data, does business logic stuff, sends result off to reducer that publishes the data back to the UI layer.

Online explanations of this suck.

Re: Vue 3.0 Updates [slides]

#116

Post by halfjoking »

GordonS wrote: post #61
Illniyar wrote: post #49

Earlier quoted context omitted.

That literally means that you aren't doing SPAs. If you aren't doing SPA then yes using React or Vue is rather a waste. However the majority of sites these days use some form of SPAs. Also under a second is a very low bar to strive to. a fast round trip to the server is 100ms. A reasonable one is somewhere around 300ms. Displaying effects to changes is often under a millisecond in SPAs and is basically impossible to…

> However the majority of sites these days use some form of SPAs Do you have a reference for that claim? I very much doubt you are correct, but I'd be interested in seeing some stats either way, if they exist.

The claim might be true among YC companies or even startups... but the majority of websites by far don't use React/Vue: https://w3techs.com/technologies/history_overview/javascript...

I'm not saying that React/Vue aren't important and drastically changing what's thought of as best-practices in web development... but just because everyone on HN uses a front-end framework for their websites doesn't mean "all websites" do it.

Re: Vue 3.0 Updates [slides]

#117

Post by yurishimo »

Zooper wrote: post #111
dmix wrote: post #98

Earlier quoted context omitted.

Just for the record most people using vue would be using Vuex: https://vuex.vuejs.org Which IMO is simpler to understand as a newbie than Redux. Maybe because it had the luxury of coming after Redux/similar projects and underpinning a simpler parent framework.

Sounds as of 3.0 it became much simpler, as vuex doesn't sound as necessary.

I’ve yet to build a Vue app that I felt needed external state management (though admittedly none are huge SPAs) but I have felt the pain in React working on a similar sized project. Just something about how the events work out of the box. React I felt like I needed to pass in functions to change parent state through a callback function in props, whereas in Vue I just emit the event and forget about it.

You can still use the function prop pattern in Vue but it doesn’t make much sense when event emission is so much simpler to reason about.

Re: Vue 3.0 Updates [slides]

#118

Post by javitury »

com2kid wrote: post #115
dmix wrote: post #98

Earlier quoted context omitted.

Just for the record most people using vue would be using Vuex: https://vuex.vuejs.org Which IMO is simpler to understand as a newbie than Redux. Maybe because it had the luxury of coming after Redux/similar projects and underpinning a simpler parent framework.

Redux is at its core super simple. Action handler gets data, does business logic stuff, sends result off to reducer that publishes the data back to the UI layer. Online explanations of this suck.

For me, how vuex works was very very easy to visualize. State, mutations and actions are very intuitive.

On the other hand, redux's reducers are harder to visualize at the beginning. Until you learn how the reducer works, every reference to "reducer" leaves you slightly confused.

I visualized redux's better with a simple example. It helps you to see how state and reducers interact.

Re: Vue 3.0 Updates [slides]

#119

Post by mlevental »

badestrand wrote: post #44
PacifyFish wrote: post #12

Earlier quoted context omitted.

Could you paste the simple script tag that makes React work without transpilation? I always thought you needed Webpack (or an equivalent) to transpile JSX into a vanilla js function the browser can interpret. If you're referring to Create React App, it uses Webpack - just preconfigured so you don't have to fiddle with it before you start building.

This is my mini React template for experiments, including JSX: https://gist.github.com/Badestrand/3609e7c3c88ba47bb9682a474...

>" rel="nofollow">https://cdnjs.cloudflare.com/ajax/libs/babel-core/5.8.24/bro...

isn't this just a little bit disingenuous

Re: Vue 3.0 Updates [slides]

#120

Post by GordonS »

halfjoking wrote: post #116
GordonS wrote: post #61

Earlier quoted context omitted.

> However the majority of sites these days use some form of SPAs Do you have a reference for that claim? I very much doubt you are correct, but I'd be interested in seeing some stats either way, if they exist.

The claim might be true among YC companies or even startups... but the majority of websites by far don't use React/Vue: https://w3techs.com/technologies/history_overview/javascript... I'm not saying that React/Vue aren't important and drastically changing what's thought of as best-practices in web development... but just because everyone on HN uses a front-end framework for their websites doesn't mean "all websites"…

Thanks, these are exactly the kind of numbers I was looking for!
Post reply on HN