Web Apps? No thanks

Web Apps? No thanks

Summary: "Web-based computing is inevitable," writes David Berlind in a recent post Step aside Google Spreadsheets. Bricklin's WikiCalc has reinforcements "99.

TOPICS: Browser

"Web-based computing is inevitable," writes David Berlind in a recent post Step aside Google Spreadsheets. Bricklin's WikiCalc has reinforcements "99.99 percent of the problems people cite as the reason they'll never move, including "the offline" and the privacy/data security problems, are resolvable."

Web Apps? "No thanks," writes ZDNet member kb2504 in response to another post by David on Google Browser Sync:

With all the stories of personal info leaked and stolen all over the place, and no REAL workable security measures in place, I'll keep my data on the PC thanks. While nobody is safe if you connect to the internet at all, I'd still rather keep the bulk of my personal data off the web. You guys can enjoy the "convenience".

ZDNet member TTech001 also questions the simplicity of browser based computing: "Moving files back and forth to some server cannot be more efficient than working with files on your local desktop and saving it to the server before you go home."

And CJames_z thinks it's thin clients all over again:

It just isn't going to happen on a large scale. And it has nothing to do with security. There are two problems: First of all, people like having their own tools. Secondly, it's going to be a long, long time before you can come even close to duplicating the full functionality of major applications on the web....[more]
See also:
  • Could Web-based PowerPoint-killers be the last straw for MS-Office? --David Berlind
  • Living a dual life - desktop and cloud --Marc Orchant
  • JavaDB: An idea whose time has finally come? --David Berlind
  • Topic: Browser

    Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


    Log in or register to join the discussion
    • As time goes on, positives will outweigh negatives.

      The network is getting faster and more reliable every day. The tools for creating web applications are getting better. The advantage of being able to access you applications from any computer, anywhere, the ability to ahare and edit simultaneously, publish instantly, are already there and are enough of a reason for many to start using web applications right away.

      But, as web applications get better, the net gets faster and more reliable, it is just a matter of time untill the majority are using web applications.

      And, don't forget, also comming is web applications that can cash themselves and the data for off-line use.
    • There is no escape from the need of a local OS

      It seems as if the only reason to try and build web apps that match desktop apps, is to try and make OSs irrelevant ? Windows in particular. The problem is, the only way to make web apps (in particular web apps that work offline) match desktop apps, is to transform the browser into an OS, so that it can provide the rich services the web apps need. Therefore by trying to escape the OS normally found on a computer, you would wind up having to create one in the browser. Therefore there really is no escape making the most versatile and rich apps (regular and Internet oriented) being dependent on a local OS.
      P. Douglas
      • Yes, but the local OS could support just a browser with mini web server and

        data store. The mini web server and data store would allow web applications to cache themselves and their data for off-line use, and there would be an automatic re-sync when re-connected.

        So, yes, you would have a local OS, but it would be much simpler, and if your computer ever fails, buy a new one and connect it to the network, and you are back in business.
        • Extending the capabilities of local OSs gives you the best solutions

          The problem is, the richer and more capable you would like your applications to become, the bigger your local OS will need to be. Eventually you will wind up with an OS looking a lot like Windows. Besides, it is generally a lot easier to work with your data locally, and synch it up to a server so you can access it anywhere. Also I?m sure if MS and maybe ISVs work on it hard enough, and the need is there, they could come with solutions that make it easy to save and move your personal computer setup from one machine to the next. (I believe Windows Server now, or will allow enterprises to load canned Windows images onto PCs within a network.)

          Therefore many of the advantages of current day web applications can be developed and incorporated into client OSs and their supporting servers, giving you the richness advanatages of a local OS, as well as global access to data and other advantages of current day web applications.
          P. Douglas
      • Not only

        [i]It seems as if the only reason to try and build web apps that match desktop apps, is to try and make OSs irrelevant[/i]

        Actually, that's only one reason. A much larger one is to make them portable (you can access them from any machine, not just the one on your desktop or whatever) and collaborative.

        That last is extremely important. A wiki is obviously much more than a text editor, because it allows concurrent editing. Likewise a collaborative spreadsheet allows a team on a teleconference to update what-if scenarios together. That last would have been [b]extremely[/b] convenient in some of the recent committee work I've done, for instance.

        Other cases aren't too hard to come up with.
        Yagotta B. Kidding
        • Actually (re: wikis)

          Wikis don't allow concurrent editing. They tell you if someone else has saved the page since you last opened it for editing and usually won't allow your over-write. But it's very close to concurrent editing.

          • Depends on the wiki

            Some do.

            $SIGNIFICANT_OTHER did quite a bit of reasearch into the available ones while she was at Intel, and there is at least one which allows concurrent editing (although not overlapping, obviously).
            Yagotta B. Kidding
    • Web Apps, Yes thanks...

      Why would webapp not be capable of offering secure local storage (this is in response to one of the quote in the blog article)? it has been demo'ed already - I can create a webapp which will keep the user's private and sensitive data locally into some encrypted data storage...I can use a local and secure storage capability such as Apache Derby or/and Java DB (which is based on the first one)...

      Not even a few years ago, most people would not have imagined what kind of applications could have been possible with today's web capabilities...We've already entered the era of read-write WEB, and data thoughtput is already a given in terms of performance - the WEB has become so ubiquitous and its capabilities are constantly evolving in a multi-dimentional space - just imagine what it will be a few years from now...