Live data from Hacker News

Vue Native (2018)

vue-native.io

71–80 of 190 posts

Re: Vue Native (2018)

#71
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 sanest MVC implementation is AppKit and classic UIKit.

Re: Vue Native (2018)

#72
post #56
post #38

Earlier quoted context omitted.

I keep vainly hoping for undo/redo, configurable keyboard shortcuts, cross-app files, app help, you know... the wins of the Windows 3.x 90s. I'm honestly amazed some (especially undo!) were shrugged away so easily.

Can you elaborate? Undo/redo in what contexts? What applications had undo/redo besides for editing things?

Apparently iOS?

Re: Vue Native (2018)

#73
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)…

As other people say, something like 10% more effort to reach 2 platforms rather than a single one.

But _also_ (and that's no small deal), these cross platform framework often benefit from a huge skill transferability from web development, eg React Native or Vue Native. This is a massive deal, it means you can get a web dev to be productive on a mobile app pretty much immediately (and potentially you use the same technology as for your web app, which itself is also a big deal)

Re: Vue Native (2018)

#74
post #13

Earlier quoted context omitted.

Ionic and quasar already allow you to make Vue on smartphones

Shoutout for Framework7. I built a test app in both Ionic and Framework7 and vastly enjoyed the experience of F7 over Ionic. For Ionic Vue is still in beta, poorly documented and had some vague errors with obtuse solutions. It didn't have all the components you might want in an app either, so less boiler plate. Framework7 has full Vue documentation, and the handful of components that aren't Vueified (Calendar, Toasts…

Ionic vue is no longer in beta, though it will take ~a year before it reach full parity support vs other VDOMs

Re: Vue Native (2018)

#75
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…

Yup thank you. Web is only now coming to terms with desktop application development world of doing things. While I support the movement, however there are too many legacy stuff in the web and how front end developer use JS like jquery type of thing to manage a document base page. Maybe there should be a mode like 'stric mode' to support two way data binding.

Re: Vue Native (2018)

#76

Earlier quoted context omitted.

Ionic and quasar already allow you to make Vue on smartphones

Quasar and Ionic aren’t native though. They give you the JS app in a browser packaged into an app. React/Vue native give you a real native byte code app.

Ionic capacitor seamlessly integrate with native plugins and you can write your own. Btw the react native js engine is much slower than the one on Ionic, at least on IOS.

Re: Vue Native (2018)

#77
post #52

Earlier quoted context omitted.

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.

but GP's team has just recently started using it

Re: Vue Native (2018)

#78

Earlier quoted context omitted.

Ionic and quasar already allow you to make Vue on smartphones

Ionic screwed me like a deck screw with their update path being more of a secret way into Mordor. Perfectly good app that can’t be compiled anymore without a full rewrite in what is effectively a completely different framework.

You had to upgrade from which version to which one?

Re: Vue Native (2018)

#79
post #52

Earlier quoted context omitted.

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.

Presumably pioneering it for their specific organisation.

Re: Vue Native (2018)

#80
post #79

Earlier quoted context omitted.

I'm curious what this means: "...my team is pioneering React Native development..." React Native has been around for 5 or so years.

Presumably pioneering it for their specific organisation.

Ah. I've never heard it put like that.
Post reply on HN