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

21–30 of 126 posts

Re: Vue 3.0 Updates [slides]

#21

Post by beaconstudios »

TekMol wrote: post #16

My feeling is that most people who use Vue or React only need a template engine. Typical use case: You have an array of objects and a template how each object should look like. So you do... {{ user.name }} let userList = new Vue({ el : '#users', data: { users: users } }) ...to make Vue render the list of objects. This is the only thing I ever use these frameworks for. Everything else I think I can implement in a bett…

as a React developer, SPAs in general are overused. Most LOB apps could (and should) still be written in a backend templated language. SPAs should be reserved for applications (or even individual components) with advanced interactive features, ie a proper web app.

Re: Vue 3.0 Updates [slides]

#22

Post by nahfamwegood »

aaaaaaaaaab wrote: post #14
yuchi wrote: post #2

I'm very happy to see React and Vue influence each other. They definitely are the highest quality frameworks out there and having two different research teams only improves the overall quality of the ecosystem. I'm a React fan, yet I really applaud all the nice stuff which is coming in Vue 3. Well done.

>research teams Lol. Writing JS libs is not research.

> Lol. Writing JS libs is not research.

LOL burnnnnn. That'll show em. Man this is great.

Re: Vue 3.0 Updates [slides]

#24

Post by avip »

aaaaaaaaaab wrote: post #14
yuchi wrote: post #2

I'm very happy to see React and Vue influence each other. They definitely are the highest quality frameworks out there and having two different research teams only improves the overall quality of the ecosystem. I'm a React fan, yet I really applaud all the nice stuff which is coming in Vue 3. Well done.

>research teams Lol. Writing JS libs is not research.

What makes you say that? People are actively earning phds researching implementations in different languages. JS is different because it’s useful? Runs in a browser?

Re: Vue 3.0 Updates [slides]

#25

Post by deskamess »

TekMol wrote: post #16

My feeling is that most people who use Vue or React only need a template engine. Typical use case: You have an array of objects and a template how each object should look like. So you do... {{ user.name }} let userList = new Vue({ el : '#users', data: { users: users } }) ...to make Vue render the list of objects. This is the only thing I ever use these frameworks for. Everything else I think I can implement in a bett…

Not sure if your use case includes automatic rendering (new/delete/mods) when the underlying data changes. If it can be done automagically (via unique id in the data) that is a big win (aka, code I do not have to write). Things like shadow DOM et al, are not something I want to implement or maintain.

Re: Vue 3.0 Updates [slides]

#26

Post by uhryks »

aaaaaaaaaab wrote: post #14
yuchi wrote: post #2

I'm very happy to see React and Vue influence each other. They definitely are the highest quality frameworks out there and having two different research teams only improves the overall quality of the ecosystem. I'm a React fan, yet I really applaud all the nice stuff which is coming in Vue 3. Well done.

>research teams Lol. Writing JS libs is not research.

That's not academic research but that's R&D. And the React team has shown they're very thoughtful about what they're building.

Re: Vue 3.0 Updates [slides]

#27

Post by TAForObvReasons »

PacifyFish wrote: post #12
whyevenbother wrote: post #10

Earlier quoted context omitted.

Maybe it's the constant React vs Vue articles that make me suspicious, but if you are referring to React when mentioning webpack / transliteration, i'd like to mention that you don't need them for React neither. It can be resumed to a simple script tag as well. I hate this misconception and wish it would just go away.

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.

In the docs: https://reactjs.org/docs/react-without-jsx.html

Unfortunately it uses ES6 features. There's no ES3/ES5 demo without JSX -- https://reactjs.org/docs/react-without-es6.html uses JSX

Re: Vue 3.0 Updates [slides]

#28

Post by tobr »

whyevenbother wrote: post #17
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.

No, I meant simply adding a tag and using react directly, in any context. That's how it was originally designed, btw. It wasn't meant only for SPAs when it was conceived, but as an addon to existing websites. The other comment gives a perfect example and there are a few tutorials (although I do agree not very mainstream) that teach React without JSX/Webpack/Babel/etc. edit: You are correct that you need transpilation…

I don’t think the comparison with JQuery vs JS is at all similar. JSX was created for React, and nearly every time you see React code it’s using JSX. Technically, each of them can be used separately, but it’s a very reasonable impression to consider JSX one of the main features of React.

JS was not created for JQuery, and you can not used JQuery without JS.

Re: Vue 3.0 Updates [slides]

#29

Post by whyevenbother »

tobr wrote: post #28
whyevenbother wrote: post #17

Earlier quoted context omitted.

No, I meant simply adding a tag and using react directly, in any context. That's how it was originally designed, btw. It wasn't meant only for SPAs when it was conceived, but as an addon to existing websites. The other comment gives a perfect example and there are a few tutorials (although I do agree not very mainstream) that teach React without JSX/Webpack/Babel/etc. edit: You are correct that you need transpilation…

I don’t think the comparison with JQuery vs JS is at all similar. JSX was created for React, and nearly every time you see React code it’s using JSX. Technically, each of them can be used separately, but it’s a very reasonable impression to consider JSX one of the main features of React. JS was not created for JQuery, and you can not used JQuery without JS.

"jQuery was created for JS, and nearly every time you see JS code it's using jQuery." Doesn't that sound like something you would hear a few years ago?

Re: Vue 3.0 Updates [slides]

#30

Post by whyevenbother »

akhilcacharya wrote: post #19
whyevenbother wrote: post #18

Earlier quoted context omitted.

So what? You can use React without JSX.

Using the createElement structure is more annoying than just doing a es6 template string in Vue.

Moving the goalpost. I'm only pointing the fact that it is possible, and saying it is impossible is false.

Personally, I don't find the function-call format that "annoying", and I think it presents some advantages neither JSX nor template strings have, along with some disadvantages (it's more verbose, like you pointed out).

Post reply on HN