21 ms·

Very essence commercializing of web apps is working against them. Interoperability, open interfaces, open data structures and last but not least reliability see

Very essence commercializing of web apps is working against them. Interoperability, open interfaces, open data structures and last but not least reliability seem to be forgotten these days where the lock-in-effect is the only thing keeping people. I don't want to be held hostage, so web apps and the cloud can kiss my shiny metal behind. I'll keep my data and apps on my own machine until ideas like sandstorm find a middle way in which I can stay in control of my data.

iofj 11y ago
Don't you think that the fact that webapps don't have interoperability, open interfaces, or datastructures, nor even a way to execute them under a debugger or own infrastructure or even read the files they create ... Don't you think that for companies like Google, Microsoft, etc. this is a feature, not a bug ? Microsoft would lose too many customers if they went full-on webapps, but everyone else won't. And customers like it ! Wtf ? But it makes sense : no install troubles, no running out of diskspace, no losing files (of course on occasion someone else loses your files. Like Amazon did a few months ago), ... But there's many false advantages, too. Webapps are most definitely not virus-proof (just ask any online banking security guy. Poor suckers), as a client side virus can change what's on the screen or just take over the browser window when you close it, or proxy the webapp, or ... But if you sell someone a program that works and they install and use it, ... well that's it. You got paid but that's the end of it. You get someone to run their business on a webapp, in the next negotiation you have the power to kill the other company's access to their own financial data. Or designs, or ... You got them by the throat.
- static_noise 11y ago
  You are describing why it is the way it is. Yes, pretty much so. There is a lot of convenience involved. The downside is that it creates mostly invisible dependencies which will break at the worst of times.

iofj 11y ago

Don't you think that the fact that webapps don't have interoperability, open interfaces, or datastructures, nor even a way to execute them under a debugger or own infrastructure or even read the files they create ... Don't you think that for companies like Google, Microsoft, etc. this is a feature, not a bug ? Microsoft would lose too many customers if they went full-on webapps, but everyone else won't. And customers like it ! Wtf ? But it makes sense : no install troubles, no running out of diskspace, no losing files (of course on occasion someone else loses your files. Like Amazon did a few months ago), ... But there's many false advantages, too. Webapps are most definitely not virus-proof (just ask any online banking security guy. Poor suckers), as a client side virus can change what's on the screen or just take over the browser window when you close it, or proxy the webapp, or ... But if you sell someone a program that works and they install and use it, ... well that's it. You got paid but that's the end of it. You get someone to run their business on a webapp, in the next negotiation you have the power to kill the other company's access to their own financial data. Or designs, or ... You got them by the throat.

static_noise 11y ago
You are describing why it is the way it is. Yes, pretty much so. There is a lot of convenience involved. The downside is that it creates mostly invisible dependencies which will break at the worst of times.