Live data from Hacker News

Vue Native

vue-native.io

21–30 of 208 posts

Re: Vue Native

#21

> Vue Native transpiles to React Native. Why would you not use react native directly then? I don't get it

It's a choice. Basically you have Java, Kotlin, C# and SWIFT for native apps, why use React Native. If you learning React is easier for web dev, then I'll say Vue is even easier for them. If you know React then Vue-Native isn't worth it.

Re: Vue Native

#22

Pardon my ignorance on the matter, and I’m truly sincere when I ask, but why does there need to be a *-native library for “each” different JavaScript framework? Why this instead of say Electron or something that seems, to me, to be more general purpose and thereby useful[1] (I’m not coupling my mobile apps to a single JavaScript framework). ... I suppose “React” is more of an API now-a-days, and so it may not be so b…

React native afaik is more about the native components, written in the target language, that receive information from the javascript code. This allows for smooth animations and in general a more responsive interface, as well as a more native look and feel than components made from html.

Re: Vue Native

#23
post #13

Pardon my ignorance on the matter, and I’m truly sincere when I ask, but why does there need to be a *-native library for “each” different JavaScript framework? Why this instead of say Electron or something that seems, to me, to be more general purpose and thereby useful[1] (I’m not coupling my mobile apps to a single JavaScript framework). ... I suppose “React” is more of an API now-a-days, and so it may not be so b…

there is some react-vr code for occulus

It just seems like an odd tooling choice. The rest of the VR ecosystem uses completely different tooling and languages. Why not build a good GUI library in one of those? I just don't see what React brings to the table I guess.

Re: Vue Native

#25
post #5

Similar projects: https://weex.incubator.apache.org/ https://www.nativescript.org/ I think Weex has better performance and lighter overhead than this(?)

I'd love to get a side by side comparison of Weex and Vue Native.

Weex lacks english documentation and most of the Weex devs are from China and support forums also tend to be in Chinese. By far RN has best documentation and plugin / package ecosystem. A full fledged app can be built using RN. Whereas it'll be hard for Weex, Vue-Native. Just search for Google Maps package for any of these frameworks, you'll have tough time finding any (barring React Native)

Re: Vue Native

#26

This is the only missing piece that has held me back from jumping into Vue. I know its not the most advantageous aspect of the framework, but my personal favorite aspect of it is the single file components. Being able to create a complete logical unit of UI of in one file feels more natural and produtive. All the speed of inline styles without the guilt and shame.

Yes! :) I've been using VueJS for awhile and my next step was to create a mobile app - either via RN or even Flutter. But, hello vue-native!

Re: Vue Native

#27

> Vue Native transpiles to React Native. Why would you not use react native directly then? I don't get it

I've been working with RN for a few months now. Good luck with that. I can't imagine another layer of abstraction.

Re: Vue Native

#28

Pardon my ignorance on the matter, and I’m truly sincere when I ask, but why does there need to be a *-native library for “each” different JavaScript framework? Why this instead of say Electron or something that seems, to me, to be more general purpose and thereby useful[1] (I’m not coupling my mobile apps to a single JavaScript framework). ... I suppose “React” is more of an API now-a-days, and so it may not be so b…

> Why this instead of say Electron

The major difference is that Electron is a way of wrapping a webapp with access to the filesystem, etc. via Node, and React Native is a way of instantiating, styling, and manipulating actual native components with JavaScript.

Re: Vue Native

#29

Pardon my ignorance on the matter, and I’m truly sincere when I ask, but why does there need to be a *-native library for “each” different JavaScript framework? Why this instead of say Electron or something that seems, to me, to be more general purpose and thereby useful[1] (I’m not coupling my mobile apps to a single JavaScript framework). ... I suppose “React” is more of an API now-a-days, and so it may not be so b…

It's normally in an attempt to "build once deploy everywhere" using tools first built as web technologies. The same selling point as the JVM for Java. In some ways Electron serves as a bit of a JVM for web, but then, that is also the utility of a browser. You can see it as an artifact of the web technology coming first and trying to port it backward to other devices. I wish we had ported some of the awesome GUI libraries from native languages forward to the web instead, perhaps when Web Assembly is ubiquitous we can finally have some coherence in tooling.
Post reply on HN