Vue 3.0 Updates [slides] • Hacker News Board

Re: Vue 3.0 Updates [slides]

#101

Post by winrid » Sat, Nov 17, 2018, 9:54 PM UTC

williamdclt wrote: post #83

orangecat wrote: post #81

Earlier quoted context omitted.

"v-model" isn't two-way binding like in AngularJS where both parent and child can modify the same data. It's just shorthand for defining a property and an event handler. Like in React, properties flow down and events flow up. See https://vuejs.org/v2/guide/forms.html

Makes sense, I've done some Angular but I'm not used to Vue. Not really related but forms really are the most painful thing to handle in all those frontend frameworks, it's driving me insane how much work has to go into them when it's dead simple with a backend framework (eg Symfony/Django)!

There are frameworks for AngularJS etc that handle most of the work in rendering forms.

Re: Vue 3.0 Updates [slides]

#102

Post by whoisthemachine » Sat, Nov 17, 2018, 10:25 PM UTC

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…

What I like about react is that it's batteries NOT INCLUDED, allowing me to choose tools best fit to the job. I think it's good that there's a healthy choice between vue and react, however!

Re: Vue 3.0 Updates [slides]

#103

Post by crooked-v » Sat, Nov 17, 2018, 10:27 PM UTC

I'm happy to see another framework moving to Typescript.

Re: Vue 3.0 Updates [slides]

#104

Post by deltron3030 » Sat, Nov 17, 2018, 10:36 PM UTC

armaxt wrote: post #36

How about the ability to create multiple components in the same .vue file? for instance I need to define a sub-component that will be used only inside my component, this is easy in React but with Vue I have to create another file to define this sub-component, this makes the project management becomes harder as the project grows

>How about the ability to create multiple components in the same .vue file?

No problem: https://www.youtube.com/watch?v=l3GHggI3_z8

As you can see, the're quite a few nested components in a single .vue file.

Re: Vue 3.0 Updates [slides]

#105

Post by pvorb » Sat, Nov 17, 2018, 10:43 PM UTC

superasn wrote: 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.

People who found a way to overcomplicate their toolchain for React will also find a way to do the same for vuejs.

Re: Vue 3.0 Updates [slides]

#106

Post by joshschreuder » Sat, Nov 17, 2018, 10:50 PM UTC

crooked-v wrote: post #103

I'm happy to see another framework moving to Typescript.

In case there are any newcomers, it's probably worth noting that just the core framework is written in Typescript, and compiled to normal JS - you are not forced to use Typescript in your own Vue code unless you want to.

Re: Vue 3.0 Updates [slides]

#107

Post by lobo_tuerto » Sat, Nov 17, 2018, 10:50 PM UTC

welanes wrote: post #65

.

Nice period substitution. ¬¬

Re: Vue 3.0 Updates [slides]

#108

Post by KaoruAoiShiho » Sat, Nov 17, 2018, 11:17 PM UTC

um_ya wrote: post #70

keerthiko wrote: post #11

Earlier quoted context omitted.

Exporting reactive JS native apps for iOS and Android is the most significant feature -- was what I would have said. I looked it up before writing this comment, and apparently Vue introduced this in June 2018. Case in point of this comment thread :)

With vue native you can use anything from the react native community in a vue application. You get the best of both worlds! https://vue-native.io/

I thought this was the preferred option? https://nativescript-vue.org/

Re: Vue 3.0 Updates [slides]

#109

Post by acemarke » Sat, Nov 17, 2018, 11:20 PM UTC

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…

Hi, I'm a Redux maintainer. FWIW, we're looking at revamping the Redux docs in the near future (see https://github.com/reduxjs/redux/issues/2590 for plans ).

If you've got any specific suggestions for improvements, please let us know! I'm always looking for ways we can make the docs better.

As a side note, React is separate from Redux, and Redux is definitely not tied to React. Here's a recent post about a team that opted to use Redux with Vue: https://snipcart.com/blog/redux-vue .

Re: Vue 3.0 Updates [slides]

#110

Post by craigzucchini » Sun, Nov 18, 2018, 12:07 AM UTC

Silhouette wrote: post #41

TAForObvReasons wrote: post #27

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.

Like you said, it depends how much you're betting on your JS to work perfectly, and who your intended market is. If all you're doing is hoping for the most optimistic JS runtime (and perfect connectivity, high bandwidth, etc.) and your site is a white screen of death otherwise, then you're not really building a robust piece of software for the web. Of course, that may not be what you're trying to do, then it's a non-issue.