Live data from Hacker News

Vue 3.0 Updates [slides]

docs.google.com

41–50 of 126 posts

Re: Vue 3.0 Updates [slides]

#41

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.

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

Unfortunately it uses ES6 features.

As an aside, is that really a problem these days? All modern browsers now offer comprehensive native ES6 support. Unless you still need to support older platforms like IE or some of the legacy mobile browsers, it's mostly a non-issue.

Re: Vue 3.0 Updates [slides]

#42

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.

http://jamesknelson.com/learn-raw-react-no-jsx-flux-es6-webp...

Re: Vue 3.0 Updates [slides]

#43

Earlier quoted context omitted.

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

Unfortunately it uses ES6 features. As an aside, is that really a problem these days? All modern browsers now offer comprehensive native ES6 support. Unless you still need to support older platforms like IE or some of the legacy mobile browsers, it's mostly a non-issue.

IE11 is holding out. Mobile Safari is hit & miss

Re: Vue 3.0 Updates [slides]

#44

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.

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

Re: Vue 3.0 Updates [slides]

#45
post #4

I think the best part about Vuejs is that how simple it is and everything just works! A vue component is still as simple as {template: 'hi'}. You don't need webpack or any transliteration for it to work. Just drop the script tag like the good old jQuery and it's working! No wonder it was so easy to switch to it. Transition from vue1 to vue2 was really simple. I'm sure the same will be true for v3.

Having started with vue, and now playing with react, I’ve found myself often thinking “this is so much simpler”. But maybe I just sucked at vue.

I think two-way-binding is the reason why many people prefer Vue to React.

If you did Ember or Angular1, Vue is much easier to grasp.

Re: Vue 3.0 Updates [slides]

#46
post #15

Earlier quoted context omitted.

Something like this? https://gist.github.com/gaearon/6668a1f6986742109c00a581ce70...

That’s without JSX. Transpilation is required in order to make use of JSX.

I wrote a tutorial about this.

In this lesson I cover JSX:

https://github.com/kay-is/react-from-zero/blob/master/02-jsx...

Re: Vue 3.0 Updates [slides]

#47

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.

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

If vue 3.0 uses proxies (as the slides say), then Vue 3 will also now require ES6 features.

Re: Vue 3.0 Updates [slides]

#48
post #39

Earlier quoted context omitted.

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.

When the user triggers a change of the underlying data, I do a roundtrip to the server and re-render the current page. I keep the time needed to do so under a second. My users regularely express how WOWed they are by the snappyness of my sites. I guess what other sites save on re-rendering html, they lose multiple times on bloated code.

„Under a second“ might be ok for websites, but doesn’t cut the mustard for web applications. People expect highly dynamic user interfaces which react almost instantaneously.

Re: Vue 3.0 Updates [slides]

#49
post #39

Earlier quoted context omitted.

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.

When the user triggers a change of the underlying data, I do a roundtrip to the server and re-render the current page. I keep the time needed to do so under a second. My users regularely express how WOWed they are by the snappyness of my sites. I guess what other sites save on re-rendering html, they lose multiple times on bloated code.

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 reach in Multi page applications.

Re: Vue 3.0 Updates [slides]

#50
post #38
post #33

Earlier quoted context omitted.

If you're just rendering HTML, you might as well do it on the server with your choice of language/framework. The power of Vue and other Javascript frameworks is in their reactivity and the ability to create extremely powerful interfaces.

I only use Vue when I need to alter the data clientside before it gets rendered. For example mark some of the users in the list as friends depending on which friends the user has stored in localStorage. If the data is ready to render while still on the sever, I do so.

Sounds like you really have a firm grasp of everything.
Post reply on HN