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

61–70 of 190 posts

Re: Vue Native (2018)

#61

Post by stall84 »

Malfunction92 wrote: post #50
user-the-name wrote: post #34

Earlier quoted context omitted.

If your goal is to actually put out high-quality apps, do not switch away from doing them natively. No cross-platform kit can compete. You are making sacrifices, sometimes big ones, in order to get the cross-platformness.

I've thought a lot about this. My biggest problem is that I'm the only one maintaining the project, and using something like vue + cross-platform would make things a lot easier than maintaining 3 different code bases (ios, android, web). My understanding is that cross-platform tools have matured enough to be used as replacements to native implementations. Is that not the case?

From the (limited) work I've done building React Native app's.. In most cases, the user is not going to be able to tell any difference from a native app.

Re: Vue Native (2018)

#63

Post by comeonseriously »

kj800x wrote: post #52
mrtksn wrote: post #22

What are the trade offs/Adventages to use cross platform tools for app development in 2021? The advantages of native iOS development, off top of my head: 1) Swift is very pleasant to use and it is fast. 2) The UI libraries that I need to learn: UIKit and SwiftUI. SwiftUI is also very pleasant to use and it is getting there. 3) No hoops to jump for integrating API that makes an App do things that WebApp cannot do. 4)…

At my work, my team is pioneering React Native development so I've got a couple of thoughts. The main benefits for us come down to the fact that we have a large existing JS web application that would take a lot of energy to port to both native platforms (we know from experience, we tried it before). Using React Native, we can share a significant amount of the data and controller layers between web and native. This al…

I'm curious what this means:

"...my team is pioneering React Native development..."

React Native has been around for 5 or so years.

Re: Vue Native (2018)

#64

Post by mrtksn »

itsoktocry wrote: post #39
mrtksn wrote: post #22

What are the trade offs/Adventages to use cross platform tools for app development in 2021? The advantages of native iOS development, off top of my head: 1) Swift is very pleasant to use and it is fast. 2) The UI libraries that I need to learn: UIKit and SwiftUI. SwiftUI is also very pleasant to use and it is getting there. 3) No hoops to jump for integrating API that makes an App do things that WebApp cannot do. 4)…

> but I think it's a fair question and I would like to know if I am missing out on something. You asked why you would want to go cross-platform, and then listed a bunch of things you like about iOS development. The fact that you aren't even sure what the Android tooling looks like answers your question, doesn't it?

I haven't asked why I would want a cross platform development. I asked how it looks compared to developing natively on the platforms you want to support.

I know very well why I would want cross platform development, it doesn't take a genius to figure it out.

The benefit is simple, write once run it everywhere. Oh wait, is that trademarked by Java? Or is their slogan Write Once, Debug Everywhere?

Re: Vue Native (2018)

#65

Post by uryga »

seanalltogether wrote: post #21
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…

Additionally, html documents inside browser windows are naturally stateless content systems, but applications have never had this constraint. The design patterns that are successful on a browser are usually overkill in application development. Android has baked a few of these stateless design patterns into their core frameworks and then spent years coming up with various support libraries to overcome them.

> html documents inside browser windows are naturally stateless content systems

what about inputs? or do you consider them stateless because their entire¹ "state" is reflected in the DOM, i.e.

  
  // *click*
---

¹ - well, except focus, open/closed for , and probably a bunch of other things

Re: Vue Native (2018)

#66

Post by criddell »

dvfjsdhgfv wrote: post #41
u678u wrote: post #23

Earlier quoted context omitted.

Hopefully one day we can get to where Visual Basic was in the 90's.

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.

Re: Vue Native (2018)

#67

Post by j45 »

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…

There's a big difference between something being new vs being new to a developer that I try to see if a developer understands.

Re: Vue Native (2018)

#68

Post by swiftcoder »

mrtksn wrote: post #22

What are the trade offs/Adventages to use cross platform tools for app development in 2021? The advantages of native iOS development, off top of my head: 1) Swift is very pleasant to use and it is fast. 2) The UI libraries that I need to learn: UIKit and SwiftUI. SwiftUI is also very pleasant to use and it is getting there. 3) No hoops to jump for integrating API that makes an App do things that WebApp cannot do. 4)…

> I would imagine that on the Android side of things are also not that different.

You would indeed imagine that, but the reality is less rosy.

1) Android is stuck on an off-brand Java stack that makes desktop Java seem pleasant by comparison. They are finally starting to make headway on replacing this with Kotlin, but most shops are still heavily invested in Java.

2) Android's UI framework is a weird hybrid of legacy and modern controls, and it only fairly recently that it has been capable of accomplishing things like a long scrolling list without memory/performance headaches. Before that everyone had to use 3rd party controls for complex or performance critical apps.

4) A lot of time spent setting up toolchains, SDKs, etc. God forbid your project incorporates C++ dependencies.

6) Google may provide Android itself, but each chip vendor then layers on their own special sauce, and finally each handset vendor layers on ever more special sauce. Add to that the historically abysmal adoption rate of new versions of android (and many vendors not providing upgraded OS versions for their older hardware), and the odds of being able to use a newly-released Google feaure/API are... not good.

Re: Vue Native (2018)

#69

Post by j45 »

danpalmer wrote: post #42
u678u wrote: post #23

Earlier quoted context omitted.

Hopefully one day we can get to where Visual Basic was in the 90's.

"Low code" on trend, many devs using Visual Studio (Code), we're nearly there.

Access too. Hypercard, and others as well.
Post reply on HN