5 ms·

> 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

by neya 8y ago

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

coldtea 8y ago
Notice how I said "some", and not "this particular solution". I haven't evaluated this, but having suffered many (similar in concept) React Native and Electron based apps as a user, I speak of my general experience with those bloated / uncanny valley monstrosities...
TeMPOraL 8y ago
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! -- [0] - https://news.ycombinator.com/item?id=17301972 https://news.ycombinator.com/item?id=17301972
- coldtea 8y ago
  >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.
  - timdavila 8y ago
    >we never managed to produce a single, great native cross platform toolkit Why can't the web+JS be that platform?
    - coldtea 8y ago
      Tons of reasons. For one, I wrote "native" above, and the web+JS aint that. But even if we ask the more general question, why "web+js can't be the great cross platform toolkit", the answer IMHO is: Web+JS are and will always be (due to the nature of the platform) inherently slower than optimal (even if "fast enough" for simple apps), use more memory, use more CPU, don't use the native facilities and so are foreign to every OS look and feel (from themes to usability features), and so on. And of course they're "bring your own theme" affairs, so no standard users can get used to, everybody does their own BS UI in SPAs and web-engine based apps (like Spotify and Atom). Add the amateur hour development practices that they enable (where a company that would previously hire actual GUI programmers can now hire some web devs and let them loose to create its app) and the picture is not nice...

by neya 8y ago

coldtea 8y ago

Notice how I said "some", and not "this particular solution". I haven't evaluated this, but having suffered many (similar in concept) React Native and Electron based apps as a user, I speak of my general experience with those bloated / uncanny valley monstrosities...

TeMPOraL 8y ago

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! -- [0] - https://news.ycombinator.com/item?id=17301972 https://news.ycombinator.com/item?id=17301972

coldtea 8y ago
>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.
- timdavila 8y ago
  >we never managed to produce a single, great native cross platform toolkit Why can't the web+JS be that platform?
  - coldtea 8y ago
    Tons of reasons. For one, I wrote "native" above, and the web+JS aint that. But even if we ask the more general question, why "web+js can't be the great cross platform toolkit", the answer IMHO is: Web+JS are and will always be (due to the nature of the platform) inherently slower than optimal (even if "fast enough" for simple apps), use more memory, use more CPU, don't use the native facilities and so are foreign to every OS look and feel (from themes to usability features), and so on. And of course they're "bring your own theme" affairs, so no standard users can get used to, everybody does their own BS UI in SPAs and web-engine based apps (like Spotify and Atom). Add the amateur hour development practices that they enable (where a company that would previously hire actual GUI programmers can now hire some web devs and let them loose to create its app) and the picture is not nice...