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

Vue Native (2018)

vue-native.io

Post reply on HN
Print view View original

121–130 of 190 posts

Re: Vue Native (2018)

#121

Post by franklampard »

rkangel wrote: post #101
cphoover wrote: post #92

Earlier quoted context omitted.

> The problem is that it's bad. I say this as someone who comes from the outside, and isn't an expert ("barely competent" in HTML/CSS is probably accurate). Basic layout of things in a way that copes with different screen sizes/orientations is a surprisingly black art sometimes. There's a lot of history confusing the issue and three ways of doing each thing. How can you say this with a "barely competent" level of exp…

> How can you say this with a "barely competent" level of expertise? I get that, and that's why I declared it. I have two reasons why I think the opinion is still valid: I'm not completely incompetent. I have produced useful web frontend work. After having spent more time on web technologies than a lot of others I still find it to be slower and harder. This point is about learning - I have done some learning in both…

I have a hard time understanding why the cost of learning web dev (CSS/html) is a sunk cost.

It’s reaping so much benefit that these experts can easily make mobile apps without learning another way to describe UI.

Re: Vue Native (2018)

#122

Post by magicalhippo »

criddell wrote: post #66
dvfjsdhgfv wrote: post #41

Earlier quoted context omitted.

I regret Delphi is a niche product now as it's quite powerful now, with native apps also for mobile platforms. Pity that the Community Edition doesn't support Linux.

Do native Delphi applications use native controls (when available)? Do they feel native, or are they their own thing? I'm thinking specifically of Java Swing applications that never felt native.

The traditional, standard, component library was built around the native Win32 controls[1].

Some time ago they acquired a cross-platform component library, FireMonkey[2], which does not use native controls.

[1]: https://docs.microsoft.com/en-us/windows/win32/controls/indi...

[2]: http://docwiki.embarcadero.com/RADStudio/Sydney/en/FireMonke...

Re: Vue Native (2018)

#123

Post by sgt »

kaba0 wrote: post #118
sofixa wrote: post #115

Earlier quoted context omitted.

The negatives of Flash are: * closed source * requires ag extra plugin to render * slow * fake sandbox that had too many bugs Flutter has none of these.

I meant it in terms of a widget with no notion of the DOM. You can’t really right click, select, only if the app creator overrides those events. Nothing native. Also, what if the creator embeds an ad inside a canvas? You would need an AI to hide it from there. So, all in all a pretty terrible direction to go..

If the creator wants an ad there, let him put an ad there or just simply stop using the app.

Re: Vue Native (2018)

#124

Post by franklampard »

speedgoose wrote: post #102
mikece wrote: post #90

Earlier quoted context omitted.

Just like JavaScript: it's bad but it is the only thing that works everywhere so it's won.

Modern JavaScript is pretty good.

Don’t even tell them.

The modern JavaScript/TypeScript is so amazing and probably the best language I have used.

I have extensive programming experience in other languages like Java, Scala, Python, Ruby, C, Lisp. But JavaScript definitely wins.

Re: Vue Native (2018)

#125

Post by karmakaze »

um_ya wrote: post #27
M4v3R wrote: post #24

Earlier quoted context omitted.

That's a dealbreaker for me. Not only you need to deal with quirks, bugs and feature-parity with lates OSes of Vue Native, now you also need to deal with the same for React Native. This is a bit too much for me, it's nice when it works but sucks when it stops to work and you spend the whole day to nail down some framework-specific issues.

It allows any react native components to work in vue native. Pretty valuable actually.

Is this not correct, can you use React Native components from Vue Native?

Re: Vue Native (2018)

#126

Post by iaml »

katsura wrote: post #110
nine_k wrote: post #72

Earlier quoted context omitted.

Apparently iOS?

iOS has undo when you shake your phone. Or what kind of undo are you referring to?

There are also gestures for it now - undo is swipe left with 3 fingers and redo - same but to the right.

Re: Vue Native (2018)

#127

Post by snarfy »

ktpsns wrote: post #5

I love functional concepts such as stateless systems, but young folks should acknowledge that two way event binding is something graphical desktop toolkits are doing since decades. For instance, Qt signal-slot mechanism https://doc.qt.io/qt-5/signalsandslots.html or https://libsigcplusplus.github.io/libsigcplusplus Furthermore, MVC is , when done correctly, a sane two way data-GUI binding. However, I have never seen…

The problem with two way data binding is it assumes a function call is free. Two way data binding breaks when a function call is many orders of magnitude slower, like over the web. You end up with classic ASP.NET.

Re: Vue Native (2018)

#128

Post by Tronno »

matchbok wrote: post #51
oakesm9 wrote: post #25

Earlier quoted context omitted.

The advantage is that you can access ~100% of the mobile market with a single codebase for about 10% extra work compared to native on a single platform. Performance is roughly the same and you have access to most of the platform features that most apps need.

10%? Try at least 50%. If you wanna do anything complicated you have to drop down to native, which is made more confusing because of the layers of abstraction. RN, never again.

Would you mind sharing more about your experience? I'm curious what you were trying to build that was too much for RN.

Re: Vue Native (2018)

#129

Post by agumonkey »

pjmlp wrote: post #91
mikece wrote: post #90

Earlier quoted context omitted.

Just like JavaScript: it's bad but it is the only thing that works everywhere so it's won.

Just like C: it's bad but it is the only thing that works everywhere so it's won.

Isn't C a sweet spot of portability and minimalism ? no matter the defects .. the previous qualities seemed to matter more. I mean there were attempts at replacing C but nothing came close to remove it right ?

Re: Vue Native (2018)

#130

Post by agumonkey »

franklampard wrote: post #124
speedgoose wrote: post #102

Earlier quoted context omitted.

Modern JavaScript is pretty good.

Don’t even tell them. The modern JavaScript/TypeScript is so amazing and probably the best language I have used. I have extensive programming experience in other languages like Java, Scala, Python, Ruby, C, Lisp. But JavaScript definitely wins.

i'm not a js hater but i'd be curious to hear what you think is so great about ts
Post reply on HN