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

91–100 of 208 posts

Re: Vue Native

#91

Post by lwansbrough »

sanketsahu wrote: post #81
lwansbrough wrote: post #66

Here's my pitch for a better ecosystem: we develop an intermediate standard for fundamental UI building blocks (divs/blocks/layers, images, video, etc.) + a layout engine, sort of like the DOM. Shells (browsers, native platforms like React Native but without the React requirement, etc.) would give JS renderers access to the lowest level painting calls available (ie. "repaint this node") along with programmatic access…

Flutter?

Flutter is closer, but it is too focused on being a framework. I'm thinking of a platform agnostic protocol with implementations in whatever language you like. Flutter is too many of things at once. If they basically ripped out each native platform's implementation and made it target the protocol I've described, then made their OOP framework target that protocol, then had the two interface using the protocol, that's what I'd like to see. That way you could write React Native on top of that new "Flutter Native Core".

Re: Vue Native

#92

Post by laurentl »

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…

Let me chime in with my perspective.

(TL;DR : I can see the use for the lazy or otherwise-occupied developer who already knows vue and needs to dabble in mobile dev)

I'm the CTO of a start-up whose core product is a set of APIs. We have a little bit of front-end we had to build in a hurry for a "special" customer (as in, special enough to not know how to interface with an API). We used vue.js because frankly that's the framework the dev with the most front experience was comfortable with. So we're starting to get up to speed on vue.js, which honestly is a pretty good framework. But let me emphasize once again that building customer-facing front-ends is not our business.

I dread the day when we bring in another "extra special" customer who absolutely needs an app to use our products... vue-native, if it's robust and stable enough, might just be a quick way to build such an app without having to learn an entire stack (on another platform, no less) for a quick one-off.

Re: Vue Native

#93

Post by ehnto »

chacham15 wrote: post #40
ehnto wrote: post #29

Earlier quoted context omitted.

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 libra…

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?

It's not constantly churning and it has matured over many years. Those are genuine benefits.

I am not a fuddy duddy holding onto old memories, I am a long term web developer watching people try to shoehorn the churning spaghetti mess of dependencies and tooling that is the javascript ecosystem back into native platforms that have dedicated clean frameworks already.

It has gotten better of course, but the only reason we have so much engineering capital in Javascript is because it runs everywhere on the web. If everyone using typescript and ES6 transpilers could have just used a better language 10 years ago they would have.

It seems backwards to go from web tech to native, because native has always had numerous advantages as a platform over the web. Everything we have in the javascript ecosystem is just us saying "man I wish we could do this thing the non-web platforms can do already"

Re: Vue Native

#94

Post by southerndrift »

lwansbrough wrote: post #71
mark_edward wrote: post #68

Earlier quoted context omitted.

Web Components?

No, because web components assume you're using the DOM. Which we definitely do not want. I want to go lower level. Give me a hashmap of nodes currently on screen. Let me design how the nodes are arranged in a render tree. Let me design how the nodes are redrawn. Let me design how the nodes are styled. I shouldn't have to compile my styles to CSS. Make the browser a rendering slave with a small but effective layout en…

Can't you do this by yourself by implementing a thin layer on top of the canvas element? What do you need more than a z-map of all of your nodes to keep track of which one is at the top and should receive mouse and touch events?

Re: Vue Native

#95

Post by yehosef »

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:

1) many people prefer Vue over React - you can google them and their reasons.

2) one of the great selling points in the React ecosystem is React-Native - you can write many parts of your code once and use both for web and native applications.

There are other solutions for this for Vue (Weex and NativeScript) but React Native has the mindshare. Perhaps there are other benefits - I don't work with apps so I don't have experience.

Re: Vue Native

#96

Post by royjacobs »

woah wrote: post #44
chacham15 wrote: post #40

Earlier 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.

Can you qualify this "lots of times" claim?

Re: Vue Native

#97

Post by re-actor »

securityfreak wrote: post #79
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.

I honestly do not understand how did a large part of the software engineering community get to this point of idiocy. Is this due to the principle of getting to the market first and quick prototypes? I don’t see a quick way back.

We are in the odd position where HTML + JS + UI framework (Vue/React) is just by far the best way to create good user interfaces. The performance hit is not going to stop anyone from using or developing software like this. There is NO good alternative.

Re: Vue Native

#99

Post by walterstucco »

matthewmacleod wrote: post #85
securityfreak wrote: post #79

Earlier quoted context omitted.

I honestly do not understand how did a large part of the software engineering community get to this point of idiocy. Is this due to the principle of getting to the market first and quick prototypes? I don’t see a quick way back.

Frankly I find your view pretty offputting. I’m not really that into the idea of JS-as-a-platform, but it obviously emerged because it fulfilled certain requirements that weren’t covered elsewhere. The “way back” from this is for people like yourself to stop dismissing others’ work as “idiocy” and start building better solutions to these problems as you see them.

It just made possible for web developers to jump on the native apps train

It's hard to think of it as an improvement

The idiocy is in the hundreds of engineering hours spent to build half baked solutions that never work as expected and never will

It's developers not wanting to adapt, while if they spent half of that effort on red or even visual basic 6 we would have end up with something better

Diversity is king, web everywhere for everything will impoverish the entire developer's community

Re: Vue Native

#100

Post by sireat »

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

Post reply on HN