Ironic the site does not seem to be responsive
Yes. Its worse than terrible on a mobile. Going to see if its open source and put a pull in for it.
Vue Native
51–60 of 208 posts
Re: Vue Native
#52Earlier 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…
React native does not compile down to native code.
Correct. It does interoperate with it though, and the built-in components are indeed in native code but called via the JS bundle. Of course, a lot of external libraries are just Views-within-Views and give up some of the nice performance benefit of the native code underneath, sadly...
Re: Vue Native
#53Site is broken on mobile. Styling issues make it undreadable.
Probably they are just people and didn't have the time to write a responsive css, which is not as simple as it sounds, especially if you are not using a grid framework.
Feel free to fork the site's code and send them a PR.
Re: Vue Native
#54Can 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?
vue is similar to react+mobx.
react in itself has no two way data binding, vue has (well, it's one wayish, but let's not argue about specifics).
Re: Vue Native
#55Pardon 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…
Christ, Electron would be truly terrible for mobile apps. All the excuses people have for its bloat ("we all have tons of RAM anyway!", "storage space is cheap!", etc) evaporate when you're running on an ARM processor with maybe 2GB of RAM and 32 to 64GB of onboard storage.
Well, those excuses are garbage everywhere. :/ All the extra electricity burned around the world would easily pay for more highly skilled devs to write a native application (source: plucked from thin air ;) ).
Re: Vue Native
#56Their website may have repurposed the look and logo of the Vue project, but (unlike React Native's relationship with React) this doesn't appear to have any official association. In particular, Evan You called it an "interesting approach" but added "not endorsing this"[1].
Re: Vue Native
#57Earlier quoted context omitted.
What is it about native ui technology that you think is better than web tech? In my experience, the singular advantage of native tech is performance. Am I missing something?
Lots of times the people on HN advocating for native ui toolkits just have fond memories of a form builder on Windows 95 when you didn't have to worry about all these different screen sizes and stuff.
Nowadays you can design responsive UIs with Interface Builder or the Android Studio equivalent with joy.
Re: Vue Native
#58It's based on react-vue[1] and It is internally using react-native.
1. https://github.com/SmallComfort/react-vue
Why but Why.
Re: Vue Native
#59Earlier quoted context omitted.
React native does not compile down to native code.
Correct. It does interoperate with it though, and the built-in components are indeed in native code but called via the JS bundle. Of course, a lot of external libraries are just Views-within-Views and give up some of the nice performance benefit of the native code underneath, sadly...
This is what I meant, and also what I meant when I mentioned that React Native pushed the boundaries (that I laid out above) -- it's a weird in-between of near-native, webview and native.
Re: Vue Native
#60Pardon 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…
Christ, Electron would be truly terrible for mobile apps. All the excuses people have for its bloat ("we all have tons of RAM anyway!", "storage space is cheap!", etc) evaporate when you're running on an ARM processor with maybe 2GB of RAM and 32 to 64GB of onboard storage.
> 32 to 64GB of onboard storage.
If only. Probably a lot closer to 4-16GB for a lot of Android phones.