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

161–170 of 208 posts

Re: Vue Native

#161

Post by Can_Not »

TeMPOraL wrote: post #156
fvdessen wrote: post #149

Earlier quoted context omitted.

They do it simply because it's the most cost effective solution overall.

Yes. It's the most cost-effective solution, because: - we haven't figured out how to make companies care about "delivering value" part of the "delivering value in exchange for money" work, and - we allow them to dump externalities on users without consequences or compensation. So the most cost-effective solution in this scheme will be a half-assed product that's barely good enough to be sellable, and which makes my c…

And the whole point of native components in Vue/react is to reduce those negative externalities, but the first thread I see in this post is criticizing Vue for sharing from react's ecosystem instead of inventing an indentical solution from scratch?

Re: Vue Native

#162

Post by qaq »

TeMPOraL wrote: post #156
fvdessen wrote: post #149

Earlier quoted context omitted.

They do it simply because it's the most cost effective solution overall.

Yes. It's the most cost-effective solution, because: - we haven't figured out how to make companies care about "delivering value" part of the "delivering value in exchange for money" work, and - we allow them to dump externalities on users without consequences or compensation. So the most cost-effective solution in this scheme will be a half-assed product that's barely good enough to be sellable, and which makes my c…

At the current rate we will soon have phones with 8GB RAM and who knows how many cores not having to rewrite same code 3 times in 3 lang. will def. be catching on more.

Re: Vue Native

#163

Post by mieseratte »

neya wrote: post #8
maxwell2022 wrote: post #6

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

A lot of us prefer Vue over React, I for one favor Vue over React personally and have been using it in all my recent projects. So, just a matter of preference for those who don't want to use React.

I'm curious, what do y'all actually like about Vue over React? I spent over two months doing proof-of-concept migration work for an AngularJS to (React-Redux|Vue-Vuex) and, other than the component-data wiring it does internally, I found it to be worse in nearly all respects.

Despite being an "opinionated" framework, Vue provides so many escape hatches and alternatives that it, in practice, hardly seems opinionated. Additionally, the templating language it promotes seems like a step backwards compared to JSX render functions. As it were, the "unopinionated" React, by offering a small handful of primitives, ends up making things simpler and more ergonomic to work with.

I really can't seem to grok why folks like Vue over React.

Re: Vue Native

#164

Post by steiner_j »

I'm genuinely confused as why this is getting so much attention. The NativeScript-Vue integration is out for over a year already. It fulfils exactly the same purpose, without the additional strange cross-compilation/transpilation.

Re: Vue Native

#165

Post by TeMPOraL »

qaq wrote: post #162
TeMPOraL wrote: post #156

Earlier quoted context omitted.

Yes. It's the most cost-effective solution, because: - we haven't figured out how to make companies care about "delivering value" part of the "delivering value in exchange for money" work, and - we allow them to dump externalities on users without consequences or compensation. So the most cost-effective solution in this scheme will be a half-assed product that's barely good enough to be sellable, and which makes my c…

At the current rate we will soon have phones with 8GB RAM and who knows how many cores not having to rewrite same code 3 times in 3 lang. will def. be catching on more.

If by soon you mean in 2 years on flagships (looking at current specs, I don't buy it), then for regular users buying regular smartphones it'll be ~7 years from now.

I don't feel like this is a valid justification for being wasteful, though.

Re: Vue Native

#166

Post by TeMPOraL »

tmd83 wrote: post #77
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?

I would say taking 1/10th or 1/100th of resource is a pretty damn big advantage even if that's just one advantage. Modern browsers are probably the most inefficient mainstream computer technology ever regardless of how useful it might have been.

Ironically, web browsers themselves are extremely optimized. They are one of the most efficient pieces of software out there. It takes actual work to screw all that up and turn it into the molasses that is modern web. Careers are built out of that work.

Re: Vue Native

#167

Post by throwaway413 »

TeMPOraL wrote: post #165
qaq wrote: post #162

Earlier quoted context omitted.

At the current rate we will soon have phones with 8GB RAM and who knows how many cores not having to rewrite same code 3 times in 3 lang. will def. be catching on more.

If by soon you mean in 2 years on flagships (looking at current specs, I don't buy it), then for regular users buying regular smartphones it'll be ~7 years from now. I don't feel like this is a valid justification for being wasteful, though.

The OPO 6 is out now with 8GB RAM, so no not in two years, let alone 7.

Re: Vue Native

#168

Post by TeMPOraL »

throwaway413 wrote: post #167
TeMPOraL wrote: post #165

Earlier quoted context omitted.

If by soon you mean in 2 years on flagships (looking at current specs, I don't buy it), then for regular users buying regular smartphones it'll be ~7 years from now. I don't feel like this is a valid justification for being wasteful, though.

The OPO 6 is out now with 8GB RAM, so no not in two years, let alone 7.

That's an outlier, pretty niche one at that.

(Personally, I didn't even realize OnePlus phones still exist - I thought they died out somewhere around OnePlus 3.)

Re: Vue Native

#169

Post by Kihashi »

mieseratte wrote: post #163
neya wrote: post #8

Earlier quoted context omitted.

A lot of us prefer Vue over React, I for one favor Vue over React personally and have been using it in all my recent projects. So, just a matter of preference for those who don't want to use React.

I'm curious, what do y'all actually like about Vue over React? I spent over two months doing proof-of-concept migration work for an AngularJS to (React-Redux|Vue-Vuex) and, other than the component-data wiring it does internally, I found it to be worse in nearly all respects. Despite being an "opinionated" framework, Vue provides so many escape hatches and alternatives that it, in practice, hardly seems opinionated.…

I got into Vue because it was much easier to approach coming from a back-end (Python/Flask/Jinja or PHP/Symfony/Twig) perspective. It made it easy to adopt small pieces and learn as I went. React probably allows this sort of thing, too, but the documentation for Vue pointed it out first thing. Since I've started working with it, I haven't gotten a compelling reason to change to react or angular.

Re: Vue Native

#170

Post by iaml »

Aissen wrote: post #151
hexmiles wrote: post #141

Earlier quoted context omitted.

What are Gibbon and Cobalt? I tried google but with no success. Do you have any link?

Gibbon: - https://medium.com/netflix-techblog/crafting-a-high-performa... - https://medium.com/netflix-techblog/building-the-new-netflix... - https://www.youtube.com/watch?v=eNC0mRYGWgc Cobalt: https://www.cobalt.dev/

I find it funny that youtube made a cool new tech specifically to render UI on tv's and yet it works like shit on any tv I encountered.
Post reply on HN