42 ms·
Very little of what you said is specific to the web. The only difference is that if you build on top of the browser, the distribution system and distributed ser
by dkersten 16y ago
Very little of what you said is specific to the web. The only difference is that if you build on top of the browser, the distribution system and distributed services layer is done for you. But you can do all of this in desktop apps too and more efficiently - but at a higher development cost.
it's on the web, they can collect (and sell) statistics much more easily
Nothing is stopping you from connecting your desktop software back to a central server in order to store statistics.
And stream ads.
I can stream adds too - I open a socket to my add streaming server and it sends me the next one. Or whatever. Nothing novel about the web here.
And perform proprietary operations without exposing their algorithm.
Again, I can do this too by following a browser/server model - I simply connect to my server and do it there. Desktop apps can use the internet too, you know.
There's no way to make a "no-cd" crack for web-based software; there's no instruction you can short-cut to get the premium version for free.
Once again, this is in no way specific to the web.
The advantage that web apps have is that everybody already has browsers installed and these browsers already contain a lot of what applications need: a way to display an interface, a means of scripting client-side in order to perform local tasks without having to cross the network and a standardised communications protocol. On the server side, there are a set of frameworks to make use of this. You could do this with other apps too, if you really wanted. The only thing web apps have over other kinds of apps is ease of distribution - because everyone already has web browsers.
On the flipside, desktop apps have advantages too. Maily performance and fine grained control over the computer and interface. In theory all of this will become available in browsers eventually, but honestly, as long as javascript is the only reasonable choice i have for client-side programming, I'm not going to be much of a fan (though NativeClient could fix this!).
If everything is moving to the browser, why are we still using fancy operating systems? Really, all we need is some local storage (for caching things, mainly), some ethernet and wifi drivers, usb drivers (for reading external drives, cameras etc), memory card reader drivers, some kind of video driver and.. well, a browser. No need for fancy GUI systems (outside of the browser), no need for other apps. No need for media players (outside of the browser) and so on. I suppose things are slowly moving this direction. Unless native client or something similar takes off, though, I'm not terribly interested - Javascript is a terrible hack of a language.
Ignoring whatever the servers will run on, of course.
- Groxx 16y agoNot specific to the web, no. But note how few have done it, and how many people resist it (application-specific firewalls and paranoia over applications "phoning home"). A large part of the point of all this is how much easier it is for the web, and how much more readily people accept it. Though how is not having a crack not unique to the web? And before you say you can send different versions of the application, remember there is copy/paste. The millions (billions?) of premium-version pirated copies of applications floating around suggest otherwise. But when was the last time you saw additional Google storage on a torrent network? And no, currently, browsers aren't up to the task of replacing desktop apps. Nowhere near. NaCl provides a rather large open door for the possibility, though, and you can bet other browsers will follow suit; it's a killer feature.
- dkersten 16y agoThough how is not having a crack not unique to the web? Its not unique to the web. It has little to do with the web and more to do with a thin-client client-server model. Take, for example, MMORPG's - these are typically dificult or impossible to crack (sure, some have replacement servers, but they're rarely as good as the original and you can do the same for SaaS web apps too, if you really wanted to). I'm mainly arguing against the idea that the webs positive features are unique to the web - they're not, they come from the webs underlying technologies (client-server, thin-client..) and these could be implemented by desktop apps, if one really wanted to. The one place where the web wins hands down is user acceptance. Everybody has a browser and nobody minds the browser phoning home, as you said, yet they are paranoid about desktop apps doing so. This is where the browser wins - the rest can be done elsewhere too. NaCl may change everyting, though, when it catches on. That will be certainly interesting to see and, while I dislike web apps right now, NaCl has a good chance of changing my mind. I'm certianly not against the things you mentioned - they ARE desireable traits, after all.