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

91–100 of 190 posts

Re: Vue Native (2018)

#91

Post by pjmlp »

mikece wrote: post #90
rkangel wrote: post #88

Is anyone else sad that we have adopted HTML/CSS as the universal lingua franca for describing views? I understand why (or at least I believe I do): HTML/CSS is an inevitable part of the ecosystem because the web is an important target. A lot of devs will know at least some, and your organisation may already have loads of them because you also need to target the web. Maybe you even already have some view code written…

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.

Re: Vue Native (2018)

#92

Post by cphoover »

rkangel wrote: post #88

Is anyone else sad that we have adopted HTML/CSS as the universal lingua franca for describing views? I understand why (or at least I believe I do): HTML/CSS is an inevitable part of the ecosystem because the web is an important target. A lot of devs will know at least some, and your organisation may already have loads of them because you also need to target the web. Maybe you even already have some view code written…

> 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 expertise? I would rather hear a well reasoned argument from someone who knows the ecosystem and its trade-offs.

Re: Vue Native (2018)

#93

Post by nolok »

rkangel wrote: post #88

Is anyone else sad that we have adopted HTML/CSS as the universal lingua franca for describing views? I understand why (or at least I believe I do): HTML/CSS is an inevitable part of the ecosystem because the web is an important target. A lot of devs will know at least some, and your organisation may already have loads of them because you also need to target the web. Maybe you even already have some view code written…

I just don't understand what happened to classical RAD from the late 90s early 00s. OK web was out of touch because no one really uses the "standard gui" anymore, even something as simple as a button has different look and behavior on every website.

But mobile app should be prime targets for it, and theming is a well understood concept for it too.

So why do we not have a proper rad tool (drag and drop my button where I want it, see the list of events, double clic onclic to edit code to run on clic event, customize onrender if I want some magic look or draw on a canvas,...).

It has got to be better than this html/js horror show.

Re: Vue Native (2018)

#94

Post by cultofmetatron »

nolok wrote: post #93
rkangel wrote: post #88

Is anyone else sad that we have adopted HTML/CSS as the universal lingua franca for describing views? I understand why (or at least I believe I do): HTML/CSS is an inevitable part of the ecosystem because the web is an important target. A lot of devs will know at least some, and your organisation may already have loads of them because you also need to target the web. Maybe you even already have some view code written…

I just don't understand what happened to classical RAD from the late 90s early 00s. OK web was out of touch because no one really uses the "standard gui" anymore, even something as simple as a button has different look and behavior on every website. But mobile app should be prime targets for it, and theming is a well understood concept for it too. So why do we not have a proper rad tool (drag and drop my button where…

Delphi is still around and they do let you drag and drop a mobile layout and target ios and android. I don't know anyone using it though.

Re: Vue Native (2018)

#95

Post by sago »

ragnese wrote: post #56
sago wrote: 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?

Is "editing things" (i.e. data) not central in the majority of apps?

Re: Vue Native (2018)

#96

Post by mrtksn »

that_guy_iain wrote: post #83
mrtksn wrote: post #58

Earlier quoted context omitted.

Please educate me, what is good? What I am missing out on? I'm no stranger to Web tech, including JS on the browser and on the server side. It's hell compared to native App development using the native technologies. I mean, it's so bad that the tutorials explaining the project setup phase can be hours long to follow. Scripts running in the background just to keep you in check and let you write more readable code that…

> Please educate me, what is good? What I am missing out on? For me, it's that you're talking about the flaws which means they're considerable.

Considerable? I don’t know, every few days I would need to restart Xcode. No big deal, really. It’s two clicks to close the app, one to launch it again but it’s annoying nevertheless.

Re: Vue Native (2018)

#97

Post by kaba0 »

sgt wrote: post #59

Flutter web is also becoming a viable option for web apps. I recently wrote a new app in Flutter and it works surprisingly well on the web, not just in native iOS and Android. It has some quirks though but I did not find anything serious.

Isn’t it still just a canvas with basically no accessibility, and all the negatives of a flash app?

Re: Vue Native (2018)

#98

Post by holtalanm »

donmb wrote: post #55

I was using Cordova with VUE.js and had fantastic results in both iOs and Android, using "Buefy" as my UI framework. I started with Nativescript and ended up in building a WebView which I then simply included. I haven't tested Vue Native yet but wanted to know why Cordova seems to be on the decrease :( I feel like I have to develop in Vue Native or Nativescript soon to not lose track. However, I always liked the Cord…

honestly, not sure about this either. Cordova works great without having to support two separate codebases for your views, which is what we all want. Vue Native, while sporting a nice HTML syntax, is just wrapping native components, which means you have to write your app specifically for native.

Re: Vue Native (2018)

#100

Post by warent »

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.

Thanks for pointing this out.

I've made a respectable living off web technologies, and the products I've built create value for many people.

Maybe it's not the sharpest knife in the kitchen and I'm not Gordon Ramsay, but the final consumer product is still pretty close to being regarded as Michelin Star quality, not as a boast but just a point of fact.

Giving an flip "XYZ technology bad!" remark usually comes across as a meme or as uninformed and snobbish. The fact is these "bad" technologies do a whole lot of good.

Post reply on HN