Earlier quoted context omitted.
It's funny because Netflix's Gibbon and YouTube's Cobalt already use some of those ideas. At least the latter is open source. Flutter is built with the same thinking. There will be some kind of convergence in the coming years.
What are Gibbon and Cobalt? I tried google but with no success. Do you have any link?
Vue Native
151–160 of 208 posts
Re: Vue Native
#152Earlier quoted context omitted.
For certain values of good user interfaces perhaps. There has got to be a better way forward for mobile UI. For desktop creating UI on something like QT designer or XAML on WPF is way more pleasant than HTML+JS+UI framework . Even Actionscript was less convoluted that this mess. I love writing React code but these abstractions are getting too elaborate. I had high hopes for WebComponents but support for those seems t…
Compared to vue, qt and all its reincarnations are a nightmare to work with.
Maybe. But it boils down to where you want to put the crap - contain it within the dev team, or drop it on your users? Obsessive trading of developer time on your end for compute use on users' end is a big part of what makes web UIs suck. Also, for keeping some of the crap on your end, native-native toolkits give you consistency and performance for free.
Re: Vue Native
#153Earlier 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.
> I find it entertaining that you post this a within 24 hours of the linus/tanenbaum rehash.
Do you have a link about this latest rehash? I tried googling without success
Re: Vue Native
#154Earlier quoted context omitted.
> Because, it solves a problem Some solutions are worse than the original problem. Besides, not everything qualifies as a problem. "I want to build a good mobile app" is a problem. "I like to use Vue and want to use it specifically to quickly build an app no matter how slow / bloated the result will be" is not exactly a problem. More like a capricious wish that was granted... It's like how "I want to eat" defines a p…
> 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, we're losing the ability to deliver fast, useful UIs!
--
Re: Vue Native
#155Earlier quoted context omitted.
Christ, Electron would be truly terrible for mobile apps. All the excuses people have for its bloat ("we all have tons of RAM anyway!", "storage space is cheap!", etc) evaporate when you're running on an ARM processor with maybe 2GB of RAM and 32 to 64GB of onboard storage.
> 32 to 64GB of onboard storage. If only. Probably a lot closer to 4-16GB for a lot of Android phones.
For a brand new phone. If everyone around you is using a phone that's less than 2 years old and purchased brand new, then you're living in a bubble.
Same issue with web apps that run just great on the developer's 9 month old iMac over a symmetrical 100/100 connection vs the typical family's 5 year old chromebook (or the 8 year old Dell at the office) and 10/768 that's also supporting a Netflix stream.
Re: Vue Native
#156Earlier quoted context omitted.
> I’m not really that into the idea of JS-as-a-platform, but it obviously emerged because it fulfilled certain requirements that weren’t covered elsewhere. Maybe they weren't covered for a reason? The ability to have your web team churn out lowest common denominator bloated JS based mobile/desktop apps was not a real requirement, more like a wish of some. Now businesses do that just because they can.
They do it simply because it's the most cost effective solution overall.
Yes. It's the most cost-effective solution, because:
- we haven't figured out how to make companies care about "delivering value" part of the "delivering value in exchange for money" work, and
- we allow them to dump externalities on users without consequences or compensation.
So the most cost-effective solution in this scheme will be a half-assed product that's barely good enough to be sellable, and which makes my computer use more electricity while being less capable of running software simultaneously.
Re: Vue Native
#157Earlier quoted context omitted.
> I’m not really that into the idea of JS-as-a-platform, but it obviously emerged because it fulfilled certain requirements that weren’t covered elsewhere. Maybe they weren't covered for a reason? The ability to have your web team churn out lowest common denominator bloated JS based mobile/desktop apps was not a real requirement, more like a wish of some. Now businesses do that just because they can.
They do it simply because it's the most cost effective solution overall.
Typical capitalism outcome.
Cheapest to produce AND worst quality. In this case by bad performance and unneeded cellphone battery drain.
These products will be dominated by superior options eventually.
Re: Vue Native
#158Earlier quoted context omitted.
They do it simply because it's the most cost effective solution overall.
Typical capitalism outcome. Cheapest to produce AND worst quality. In this case by bad performance and unneeded cellphone battery drain. These products will be dominated by superior options eventually.
> These products will be dominated by superior options eventually.
Would love that to happen, but all the other market sectors suggest otherwise. "Cheapest to produce and worst quality" seems to be all that's available to majority of the population.
Re: Vue Native
#159Earlier 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.
It's all about developer productivity and nothing else. Well, maybe a healthy dose of cargo cutting. But anyway, no care is really given anymore about resource usage, etc because all of that is abundant. I personally don't like it as I think it's wasteful and careless.
> no care is really given anymore about resource usage, etc because all of that is abundant.
They're abundant for people who you only think about themselves. Who believe that their application will be the only one running on the machine. Which may be the case if you're developing software for touchscreens on a factory floor, but is definitely not true for end-user software, and doubly not true for anything on the web.
Re: Vue Native
#160Can someone explain what the differences are between React and Vue? Why is this a good idea and what benefits would it afford me as a React Native developer?
Evan said he doesn't agree with everything but said it is one of the more reasonable discussions about the topic.
https://www.reddit.com/r/javascript/comments/8o781t/vuejs_or...