Brad Neuberg, Google Gears, and the Future of the Web 65
Linux.com has an interesting look at Google Gears and one of its leading evangelists, Brad Neuberg. "For Neuberg -- as for most developers -- the idea of expanding the Web's capabilities is intriguing in itself. But both inside and outside Google, his argument is that there's more at stake than just a particular piece of technology. In fact, he does not even seem particularly concerned whether Gears or some rival project takes on the role he envisions. What matters, he says, is that finding a solution to the problems of the Web is essential not only to the continued evolution of the Web, but also to its continued freedom. "
Fairly Rhetorical... Maybe I didn't understand? (Score:3, Insightful)
am i glad (Score:2, Insightful)
Re:Why does the web need to evolve (Score:3, Insightful)
Heh, sorry, couldn't resist.
Re:Why does the web need to evolve (Score:5, Insightful)
Because getting a fundamentally new common runtime environment and/or protocol to all people is f'ing hard. Especially now that the 'net has matured. With maturity comes momentum and inertia.
Re:Google vs. Ajax (Score:5, Insightful)
AJAX is a method to shoehorn functionality into a trifecta of legacy platforms that was never really designed for it. Like retrofitting a horseless carriage with a honda civic engine and bolting on some wings, a rudder, and a propeller with the intent to fly across the atlantic.
Just because you've gotten it to fly doesn't mean you've invented a modern aircraft.
Re:Why does the web need to evolve (Score:5, Insightful)
When you don't evolve stuff you have a very good chance to end up with a whole bunch of ugly ad hoc fixes.
will they keep my data for 10 years (Score:4, Insightful)
Re:Why does the web need to evolve (Score:3, Insightful)
Let's not talk about enabling things in different ways, let's talk instead about how, after all these years with ever-increasing hardware performance, we're building layers upon layers of inefficient software so we can have crappy application performance all over again. Trying to run applications with Javascript in a browser on a mobile phone, can it get more wasteful than that?
Use Java, it's not perfect, but it's widespread, it gets the job done and is reasonably fast. Until we have a less bloated and equally widespread language, that is...
Re:Why does the web need to evolve (Score:3, Insightful)
One of the problems is data. I want access to my data. I want access to it anywhere. When I'm at a restaurant, I want to be able to pull out my phone and check my calendar, my mail, even open a file on my desktop. When I'm on a business trip, I want the same access on my laptop.
There are lots of solutions to the data problem--some of them are fairly old. IMAP is a really handy protocol for keeping your mail accessible from just about anywhere, for example.
The other problem is user-friendlyness. Consistency is part of this. There are lots and lots of Internet users who, when confronted with a new and unfamiliar interface, will simply freeze up. I'm sure that it's largely psychological, but ultimately, the underlying cause is irrelevant. People want consistency in how they access their data.
The solution to this problem lies in Google Gears and similar technologies. It lies in allowing the web browser to be a portal into your data (though allowing access in other ways is important, too, so that people who don't mind other, more efficient interfaces can use them.)
Google handles both problems simultaneously, and quite well. If I want to use the Google Mail interface while I'm offline, I can. If I want to access my data without using javascript in a browser, I can do that with either IMAP or POP.