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

171–180 of 190 posts

Re: Vue Native (2018)

#171

Post by jarek83 »

mmcnl wrote: post #156
jdjfktkrnj wrote: post #131

Earlier quoted context omitted.

I've used pretty much all GUI frameworks - raw Win32, MFC, WinForms, wxWindows, Qt, WPF, native Android and iPhone. HTML/CSS is vastly more powerful and productive, especially when using something like React/Vue. It's not because "web devs who don't know anything else". HTML/CSS is just a superior technology. No wonder that even traditional GUIs are moving this direction - Qt with QML, windows with their new Win10 fl…

Probably an unpopular opinion but I wholeheartedly agree. I think HTML/CSS is excellent.

Have the same feelings about HTML/CSS and even similar towards JS. I believe that if one gets a grasp of it, then CSS is extremely easy now, compared to like 5-6 years ago, where on top of CSS itself, you had to be good with all the quirks for IE and other browsers.

If today someone tells that CSS is hard, I honestly get stunned. I wonder if the idea of "everyone can code" might be root cause of current state. I mean - if after some time you cannot get intermediate CSS skills, then I'd say that web programming (and maybe any other) is not for you.

It was with the boom of Tailwind CSS when I started to see a lot of comments like "OMG this framework is great - CSS was always hard for me, now I can do much more".

Re: Vue Native (2018)

#172

Post by that_guy_iain »

mrtksn wrote: post #96
that_guy_iain wrote: post #83

Earlier quoted context omitted.

> 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.

> 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.

You literally considered it while writing your list. Therefore literally considerable.

Re: Vue Native (2018)

#173

Post by pjmlp »

c-smile wrote: post #143
nolok wrote: post #93

Earlier quoted context omitted.

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…

> classical RAD from the late 90s early 00s. RAD, a.k.a. UI-nailed-down-to-pixel-grid approach, has died immediately after we've switched from 640x480 pixel screens to variety of display and devices. If in doubts think about Adaptive and Responsive Designs ( https://en.wikipedia.org/wiki/Responsive_web_design ) in regards of RAD.

Only for the clueless developers that never bothered to learn how to use layout managers.

Re: Vue Native (2018)

#174

Post by pjmlp »

cultofmetatron wrote: post #94
nolok wrote: post #93

Earlier quoted context omitted.

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.

Delphi scene is still quite active in Germany, enough to keep getting articles on the Windows and .NET developer related magazines, and a yearly conference.

Delphi suffers from the mismanagement from all its owners, and given its target market, you will usually see it being used across corporations that don't think twice about paying for SAP and Oracle licenses.

Re: Vue Native (2018)

#175

Post by cultofmetatron »

pjmlp wrote: post #174
cultofmetatron wrote: post #94

Earlier quoted context omitted.

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.

Delphi scene is still quite active in Germany, enough to keep getting articles on the Windows and .NET developer related magazines, and a yearly conference. Delphi suffers from the mismanagement from all its owners, and given its target market, you will usually see it being used across corporations that don't think twice about paying for SAP and Oracle licenses.

its a real shame too because the pascal langauge is quite nice and would hold its own against zig or c++. I would even learn the free version and potentially invest in the paid version if it ran on osx or linux. Anything thats windows only is a hard no for me.

Re: Vue Native (2018)

#176

Post by IgorPartola »

The_rationalist wrote: post #164
IgorPartola wrote: post #146

Earlier quoted context omitted.

I initially used it with version 1/Angular 1.x. Then when Angular 2 was basically a complete rewrite from scratch Ionic did the same. For a little bit I was still able to compile the code but quickly their tools became unavailable and unusable.

You were very early in the history of Ionic, I understand you :( but such breaking change should not happen anymore at this scale

It's true. But also I consider Angular 2+ to be inferior to other similar frameworks. It was overengineered to no end had as much to do with Angular 1.x as a space shuttle has to do with a horse buggy. I remember looking at how they proposed to specify templates via `` template strings as part of the JS code, making their template language completely unreadable and thinking how that's such a step back in usability compared to how Angular 1.x did it, which was basically what Vue.js does.

And I do still have some scars that haven't fully healed from that transition. Look at Vue's evolution from 1.x to 2.x to 3.x. The new way to create components in Vue 3 is what Douglas Crockford proposed way back in like 2008. Except it's reasonably worse for code readability compared to Vue 2.x because it is completely unstructured. And at one point the Vue team was talking about taking out half the features that I routinely use in Vue 2.x such as $emit()/$on(), watchers, etc.

I don't have as much experience with React, but from what I understand they break compatibility much more frequently than Vue does. Plus, JSX is a very polarizing tech and I am firmly on the side that dislikes it.

Compare all of the above with a project like Django where backwards compatibility is maintained for years and developers consider it a big cost to break features. It's a much more carefully developed project and it makes running the code much easier. The template syntax has not changed in what, 10 years at least? In the meantime how many JS frameworks have we seen rise and fall? As far as I am concerned, every time a framework or library update breaks my application, the framework is imposing a cost on me. Adding new features and refining existing features? Fine. Breaking the world because someone didn't like how $emit()/$on() worked? That's like if the Linux kernel decided tomorrow to switch to using Windows syscalls because they got a Windows developer on the team.

Re: Vue Native (2018)

#177

Post by user-the-name »

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?

For simple apps, you can get away with it.

If you are aiming for more than the basics, you'll run into trouble or impassable roadblocks.

Re: Vue Native (2018)

#178

Post by dirtnugget »

agumonkey wrote: post #130
franklampard wrote: post #124

Earlier quoted context omitted.

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

It is pretty damn powerful and quite elegant. What do you find bad about it?

Re: Vue Native (2018)

#179

Post by pjmlp »

cultofmetatron wrote: post #175
pjmlp wrote: post #174

Earlier quoted context omitted.

Delphi scene is still quite active in Germany, enough to keep getting articles on the Windows and .NET developer related magazines, and a yearly conference. Delphi suffers from the mismanagement from all its owners, and given its target market, you will usually see it being used across corporations that don't think twice about paying for SAP and Oracle licenses.

its a real shame too because the pascal langauge is quite nice and would hold its own against zig or c++. I would even learn the free version and potentially invest in the paid version if it ran on osx or linux. Anything thats windows only is a hard no for me.

You can still help improve and contribute to FreePascal and Lazarus on that case.

Re: Vue Native (2018)

#180

Post by uryga »

seanalltogether wrote: post #151
uryga wrote: post #65

Earlier quoted context omitted.

> 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

In this context stateless usually refers to access to the wider system. When an html page loads, it has no state it can access right away, it has only raw data in the url and cookies. You are constantly having to recreate the state of the system as a user moves from one page to another. Design patterns like react are a natural fit for this system, its turtles all the way down. Applications on the other hand start the…

ah gotcha! for some reason i thought you were talking at the component level, not app level.
Post reply on HN