Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vue Native

vue-native.io

Post reply on HN
Print view View original

111–120 of 208 posts

Re: Vue Native

#111

Post by hycaria »

neya wrote: post #33
htormey wrote: post #17

Can someone explain what the differences are between React and Vue? Why is this a good idea and what benefits would it afford me as a React Native developer?

This page is a good start, it discusses the differences in detail: https://vuejs.org/v2/guide/comparison.html My personal experience wasn't that positive with React and then, the whole treatment of JSX as a first class citizen isn't really my style (although you're allowed to use React without involving JSX). Vue just feels more mature (personal opinion) and much, much easier to reason your code about, down the line…

On topic of vue, I've been working on one app for a few months now, and I'm having a hard time maintaining clear code, especially for nested components. I often resort to Vuex to share info between components, which might not be the best solution...

Also my app mainly revolves around a map vizualisation, and gmaps api is a pain to manage, bloating my code. Everything in my project works fine btw and I have great pleasure developing using Vue, but I'm sure I could be more elegant/efficient. Yet it's rather hard to find complete open vue projects online to check code organisation, so how can I get better on that aspect ?

Re: Vue Native

#112

Post by Illniyar »

rubyn00bie wrote: post #12

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…

Cordova is the "electron" equivalent for mobile. I.E. running a browser rendering engine embedded inside an app.

There are 2 main reasons for making (or using) the *-native libraries as opposed to using a browser rendering approach -

1- performance. Html and CSS are insanely bloated specification for making an app. There is really no way for a browser to rival the performance of a native app. This comes into play in mobile more then desktop and is really visible when dealing with animations and very large lists/tables.

2- native looking UI. using electron you can fake a webapp to look like a native app, but it will never have all of the edge cases (for example some keyboards don't open in a browser. Web inputs behave differently then native inputs. And of-course animations).

You can think of the Native part in react-native or native-script etc... as native ui components. Which is what all of these technologies are attempting to achieve - having the look and feel of the native components of each OS while keeping the logic and layout code the same.

As to why vue-native, react-native, nativescript (angular) etc... rather then having a single base where you can use multiple different frameworks on top - nativescript is trying to do that. react-native is built in such a way that only virtual dom diffing based frameworks can work with it (which is why vue can while angular can't)

Re: Vue Native

#113

Post by neya »

codesternews wrote: post #58

It's based on react-vue[1] and It is internally using react-native. 1. https://github.com/SmallComfort/react-vue Why but Why.

Because, it solves a problem. I'm sorry, but, outside of the "let's use react for everything" bubble, people believe in different ideologies and use different frameworks to accomplish similar tasks. One of them is using Vue for web applications, and now thanks to this new project, the same Vue developers can also make use of Vue to build their mobile apps.

What it uses under the hood isn't really a concern for me as a Vue developer as long as I'm able to develop mobile apps with it.

> Why but Why.

Sorry, but this comment seems arrogant. As though just because it's out there on React, others aren't entitled to opine differently or use different frameworks?

Re: Vue Native

#114

Post by Illniyar »

danielrhodes wrote: post #72
hardwaresofton wrote: post #31

Earlier quoted context omitted.

I'll try and boil it down to some points that hopefully build on each other: - In the mobile development there are a few approaches, including but not limited to: full-native, near-native, and webview (these aren't official terms, I just made them up) - "full-native" is using Java on Android, Swift/ObjC on iOS, generally implying using all the tooling/patterns/etc that come. This is the hardest in terms of learning c…

> The existence of React Native is a huge difference-maker for react. If you want to sell your team on react, the ability for a frontend developer to easily handle mobile application development is a strong selling point. The reality is that while it may ease the transition a bit, your front-end developer will be having to dip into Swift/Obj-C often enough that eventually the supposed benefits here are moot. Personal…

I can tell you, from experience building multiple apps in production from scratch, that that's not the case. You practically never get to touch Obj-C or Java, and if you do it's usually to tweak a line or two in some third-party library which requires little to no knowledge of Obj-C or Java.

Re: Vue Native

#115

Post by Illniyar »

neya wrote: post #110
spicyj wrote: post #47

Earlier quoted context omitted.

> I re-wrote my entire teaching syllabus for my programming course to use Vue instead of React, simply because it's much better to maintain Vue apps rather than React apps after 6 months, which is the most important value add for me in any framework. Why do you find it harder to maintain React apps after 6 months?

One of the main reasons - JSX. Contrary to popular belief, JSX is all cool until you're in a situation where you need to maintain the app you wrote. I know React can be written without JSX as well, but frustratingly most documents/resources online are all examples with JSX. And then, this: https://twitter.com/thomasfuchs/status/810885087214637057

I find it the other way around actually. It's much easier for me to maintain JSX then using an html template engine.

Re: Vue Native

#117

Post by jbverschoor »

hardwaresofton wrote: post #38

I prefer NativeScript[0] & it's vue-specific extension NativesScript Vue[1] due to NativeScript's ability to work with more than one paradigm/framework. NativeScript enables any Javascript application to become a mobile app (along with ones built in Angular and Vue) and I think that's pretty great. [0]: https://www.nativescript.org/ [1]: https://nativescript-vue.org/

And there's no need to make bridges. Simply access the native API from javascript/typescript

Re: Vue Native

#119

Post by freddie02 »

sireat wrote: post #100
codesternews wrote: post #58

It's based on react-vue[1] and It is internally using react-native. 1. https://github.com/SmallComfort/react-vue Why but Why.

Vue Native is a bit of a misnomer then. The layers of abstraction keep adding up. Tortoises all the way down. Next thing someone will incorporate jslinux into this mess

https://node-os.com/

Re: Vue Native

#120

Post by k__ »

jbverschoor wrote: post #117
hardwaresofton wrote: post #38

I prefer NativeScript[0] & it's vue-specific extension NativesScript Vue[1] due to NativeScript's ability to work with more than one paradigm/framework. NativeScript enables any Javascript application to become a mobile app (along with ones built in Angular and Vue) and I think that's pretty great. [0]: https://www.nativescript.org/ [1]: https://nativescript-vue.org/

And there's no need to make bridges. Simply access the native API from javascript/typescript

NativeScript simply binds to all native APIs by default?
Post reply on HN