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

Vue Native

vue-native.io

Post reply on HN
Print view View original

181–190 of 208 posts

Re: Vue Native

#181

Post by paulie_a »

ergothus wrote: post #105
securityfreak wrote: post #79

Earlier quoted context omitted.

I honestly do not understand how did a large part of the software engineering community get to this point of idiocy. Is this due to the principle of getting to the market first and quick prototypes? I don’t see a quick way back.

I find it entertaining that you post this a within 24 hours of the linus/tanenbaum rehash. Getting crap done counts for a lot. Web, and hci in general, isnt figured out well at all, so we can spend a few decades pursuing an ideal we don't even have defined...or we can get stuff done. If you are arguing for some specific non-"idiocy", please, explain why your version hasn't taken off.

> getting crap done

Yeah you end up with crap.

Re: Vue Native

#183

Post by mieseratte »

Kihashi wrote: post #169
mieseratte wrote: post #163

Earlier quoted context omitted.

I'm curious, what do y'all actually like about Vue over React? I spent over two months doing proof-of-concept migration work for an AngularJS to (React-Redux|Vue-Vuex) and, other than the component-data wiring it does internally, I found it to be worse in nearly all respects. Despite being an "opinionated" framework, Vue provides so many escape hatches and alternatives that it, in practice, hardly seems opinionated.…

I got into Vue because it was much easier to approach coming from a back-end (Python/Flask/Jinja or PHP/Symfony/Twig) perspective. It made it easy to adopt small pieces and learn as I went. React probably allows this sort of thing, too, but the documentation for Vue pointed it out first thing. Since I've started working with it, I haven't gotten a compelling reason to change to react or angular.

> React probably allows this sort of thing, too, but the documentation for Vue pointed it out first thing.

That's actually a pretty good difference I hadn't really thought about from the other perspective. React does a good job explaining the how and why, but is a bit more clinical leaving the last-mile as an exercise to the reader whereas Vue seems a bit more focused on coaching you.

I, personally, found Vue's documentation to be a bit less in-depth than I like and hadn't considered folks would prefer Vue's.

Re: Vue Native

#184

Post by pier25 »

Considering there is already Weex and NativeScript with Vue, what does this add?

Personally I think Flutter will become the dominant cross platform solution in 2020 or so. ReactNative has always seemed like a hack to me.

Re: Vue Native

#185

Post by jaegerpicker »

re-actor wrote: post #97
securityfreak wrote: post #79

Earlier quoted context omitted.

I honestly do not understand how did a large part of the software engineering community get to this point of idiocy. Is this due to the principle of getting to the market first and quick prototypes? I don’t see a quick way back.

We are in the odd position where HTML + JS + UI framework (Vue/React) is just by far the best way to create good user interfaces. The performance hit is not going to stop anyone from using or developing software like this. There is NO good alternative.

I'm almost at a loss for words. The web stack is frankly one of the worst ways to create a good UI. The best UI's typically have three key area's:

- It's easily discoverable by the user - The web is typically horrible at this. Custom controls, look and feel's, and a severe lack of common UI patterns. Native app's have this in spades.

- It's performant - Native wins this hands down everytime. The web stack lacks threading and one of the major keys is to NOT do work on the main thread for a great UI. The vast majority of web dev's have never even thought about threading.

- The design puts features in a place the user can easily and quick get to. This has little to do with the technology platform.

Bottom line is the web stack is at a MAJOR disadvantage for building a UI. The only use for it on mobile is that developers refuse to put in the work to learn how to do the platform justice.

Re: Vue Native

#186

Post by coldtea »

TeMPOraL wrote: post #154
neya wrote: post #144

Earlier quoted context omitted.

> Some solutions are worse than the original problem. Wow, that's a pretty harsh claim. This was just released and you already think it's worse with no sort of data to back up your claims. Sorry, that's not a sound argument.

You still think it's about Vue Native. It's not. It's about using web stack for desktop applications . This is a "solution worse than the original problem". And the damage is done. This[0] comment by 'm_fayer elsewhere in the thread is quite chilling. Actual native toolkits are rotting, as big companies join the web-for-everything bandwagon. Not only delivering bloated applications with toy-like UIs becomes the norm,…

>And the damage is done. This[0] comment by 'm_fayer elsewhere in the thread is quite chilling. Actual native toolkits are rotting, as big companies join the web-for-everything bandwagon.

What's worse is that actual native toolkits are rotting, while at the same time we never managed to produce a single, great native cross platform toolkit -- even less so a great cross platform one.

Not because it's impossible, but because no major player cares (they have their own platforms), and OSS attempts like Wx and GTK+ don't have the manpower.

Re: Vue Native

#187

Post by Aissen »

iaml wrote: post #175
Aissen wrote: post #174

Earlier quoted context omitted.

Most probably you're not using a cobalt-based YouTube app yet.

Is there a list of platforms that use it?

Not AFAIK, but maybe someone more knowledgeable can chime-in.

Re: Vue Native

#188

Post by spraak »

pier25 wrote: post #184

Considering there is already Weex and NativeScript with Vue, what does this add? Personally I think Flutter will become the dominant cross platform solution in 2020 or so. ReactNative has always seemed like a hack to me.

What about it seems like a hack? Why do you think Flutter will become dominant?

Re: Vue Native

#189

Post by mlsarecmg »

sireat wrote: post #139
mlsarecmg wrote: post #132

Earlier quoted context omitted.

Xaml and Wpf? Qt? I am honestly asking you, have you worked with React before? XAML has a learning curve of 2 years and more to get to expert level. I developed with it for more or less 5 years and i still have nightmares. Qt and the others are all imperative layout inflaters. React was a revolution, maybe the first cross platform paradigm that actually made sense. A learning curve that doesn't span more than a day.…

I love writing React code and it is easy to get up to speed there. I abhor the mix of HTML/CSS for UI design. I'd rather code UIs in Actionscript. The web browser as an abstraction for general use UIs is just not ideal. XAML might be a company induced mess underneath but my point is that you don't have to be XAML expert to make nice interfaces. I made CRUD apps on WPF and rarely did I have to touch XAML directly. I h…

Well i give you that, css is what it is, but even with basic css knowledge, making a dropdown appear anywhere you want is not hard: https://codesandbox.io/embed/w7499vxrzk

It could be better, but it's even got a proper grid system now, close to wpf's. From what i remember though, wpf's styles also had some rough spots.

Re: Vue Native

#190

Post by stefanfisk »

lwansbrough wrote: post #106
danpalmer wrote: post #101

Earlier quoted context omitted.

While I admire your hopefulness that this could solve the problems, I don’t think it will for two reasons. 1. This is what the DOM is, to some extent. All those components on the page are “native” components, we have declarative markup for them (HTML) and we can script them. They are “rendered” by native code in browsers which are some of the most highly optimised codebases around. 2. The API design for JS and for hi…

Your UITableViewDataSource is a common problem with big JS applications, and has been solved to some extent with the same optimizations you've mentioned. However because JS and HTML is what it is, it has to be solved on a per-library basis (React Virtualized List, Vue Virtualized List, etc.) The problem remains that the JS renderer does not have access to those low level draw calls to optimize performance further. As…

AFAIK all virtual lists break native searching in the browser, so sadly the problem is far from solved
Post reply on HN