Google and Their Server Farm
JR writes "CNet has a very interesting story about Google, operating systems, and where Google may be going. The upshot is that they may make OS issues totally irrelevant by supplying everything anyone needs over the web from their mega-server-farm."
"Ajax, which is short for Asynchronous JavaScript + XML, combines JavaScript, dynamic HTML, and XMLHTTP to, in essence, let you build Web-based applications that run as quickly and seamlessly as local software."
Great. If the author of the article gets her pie-in-the-sky dream, the future of virtually all client-side computing will lie in the hands of javascript code. For certain applications, like ones with small, text data sets, a system like Ajax could "feel" like a desktop application. The bandwidth just isn't there for video or even industrial photo work. I wouldn't want to run a batch script to modify 5,000 images in the Ajax analog of Photoshop. Better not be a fiber network without any limits on network transfer.
Besides that, who wants anything but light-weight or at least, non-critical, data and applications to be out on the network. Gmail is a perfect network application, but my financial software or any number of other things? No thanks.
I Want To Believe
Along with about 1,000 other dot-com start ups.
Thin-Client computing by another name, again. Wasn't convinced 20 years ago. Still not convinced now. I don't want to have a useless PC just because I stopped paying the $20 a month subscription to the applications.
Get a free iPod Nano 4GB!
Seriously if I had a dime for everytime someone predicted the demise
of the desktop, I'd have a couple of bucks.
Here is the problem I have with her theory. Her points were all
logical and well laid out, essentially that most people aren't system
administrators and that they don't back their data up, don't secure it
etc. While that is true, it doesn't necessarily lead to people giving
up the desktop in favor of a thin client. Giving up your desktop is
an emotional decision, and there are a lot of factors that weigh
against that.
In the long run, maybe ten, fifteen or even twenty years in the
future, this type of service may be much more prevalent. But I don't
think something like this will change over night. Think about how
much computer systems have really changed in the last ten years. Not
that much if you really stop to think about it. What she is
predicting is a *massive* paradigm shift to say the least. Microsoft
didn't have the clout to pull it off, probably because no one trusts
them enough. Do you trust Google enough to give them *all* of your
data? I'm not sure I trust *anyone* that much.
Doug Tolton
"The destruction of a value which is, will not bring value to that which isn't." -John Galt
In the future, the network will be just as dependable as any other public utility. When "the network is down", people will treat it just like when the power's out today.
I don't know about other folks in general, but I do know that I like my privacy. I'd rather have a computer on my desk, behind a firewall, where I can keep my private information private. It's all well and good to say that storing your data on Google or Yahoo or MSN allows you to access it from any computer on earth, but you run the risk of the computer you are at copying the information you access.
Wether it's a malicious keylogger, trojan, or simply the paging space / file, your information get copied to the PC at the internet cafe you are using. Suddenly your private information is no longer private. Any savvy computer-literate person could access that copy of your data. Give me a laptop or desktop where I can encrypt the data and only I have the decryption passphrase any day.
If "disco" means "I learn" in Latin, does "discothèque" mean "I learn technology"?
I somehow doubt Google is going that direction. Don't forget their main goal, to own all information and make it availible to everyone on this planet.
The idea of a GoogleOS doesn't really match with that.
>they may make OS issues totally irrelevant by supplying everything anyone needs over the web from their mega-server-farm
yeah, try that line again when 90% of their stuff isn't (USA + Windows only) and/or beta.
I am hoping that with the arrival of broadband we can get to run our own web, email and im servers and not rely on the ISP for anything more than the transport layer.
Google should only have access to information you want to be public and nothing more.
Uh huh...
http://today.java.net/jag/Fallacies.html
Essentially everyone, when they first build a distributed application, makes the following eight assumptions. All prove to be false in the long run and all cause big trouble and painful learning experiences.
1. The network is reliable
2. Latency is zero
3. Bandwidth is infinite
4. The network is secure
5. Topology doesn't change
6. There is one administrator
7. Transport cost is zero
8. The network is homogeneous
Agile Artisans
Oh, wait, that was two buzzword generations ago. How many words are there for "mainframe" anyway?
Have you read my blog lately?
Amen, brother.
It's a sure sign of bloat and poor MS engineering that a mail program like Gmail, running javascript, beats the hell out of Outlook running on a local machine.
I don't think a plan like this will ever gain acceptance more than a small percent of computer users and here is why:
- The first thought that came to mind is business. The company I currently work at would have a heart attack if anyone suggested using a thin-client like solution with Google storing all the data. So I guess Google might sell their technology (like they currently do with their search servers) but this really wouldn't be any different than buying a file server and desktops.
- I don't see bandwidth getting fast enough in even 5 or 10 years to support a video or photo editing app. I can't even imagine having to upload a whole DVD's worth of video to Google before I could start to work with it.
- Another similar point would be application load time. Google Maps and other Axis based technologies load and run fast because there is a relatively small amount of JavaScript being sent to the browser. Could you imagine something the size and complexity of Microsof Word being sent to your browser everytime you wanted to edit a document? I think something like that would bring any browser to a crawl.
- What about customization? I like to be able to install new software on my computer. The few times I have had to deal with shared hosting for websites, it has been annoying that I couldn't install new software that I wanted to try out. Especially when my host had outdated versions of something like PHP or MySQL.
So, those are my thoughts. The only crowd I can really see this appealing to are the WebTV, just surf, email, and edit docs crowd. They might be really happy not maintaining a computer and having their data available anywhere. However, I think a small portion of computer users would fit into this category.
Personally, I would much rather just use VPN to access my home shares while on the road than have to use some sort of thin client.
What Google or someone else should really do is create VPN software that is easy enough to use that anyone can set it up. I think that would appeal to many more people than a thin-client. Plus as hard drive space gets cheaper and cheaper, it shouldn't be an issue to have the same software installed on your laptop as your desktop.
SIGFAULT
Interesting theory. Do you trust google more than EquiFax? Or ChoicePoint?
the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff
And I suspect that Google has learned a thing or two in their time about the Internet . . . they're far from "first building a distributed application".
No one ever managed to topple IBM's mainframe monopoly. It was rendered irrelevant by the arrival of smaller computers. It may very well be that Microsoft's monopoly on the PC Desktop never ends, but eventually nobody will care because the PC Desktop becomes irrelevant.
What all this tells us is that Network Computing was a good idea after all. One might even consider it inevitable. What was a bad idea was the Ellison/McNealy idea of Network Computing, where you had to throw away all your existing apps and go to 100% Pure Java applications across the board. This time it's being done right -- gradually, one app at a time, and with an easy to follow migration path. I hope it continues.
Tired of FB/Google censorship? Visit UNCENSORED!
Just because something was tried and the implementation failed does not necessarily imply that the idea is bad or unworkable.
The smartest man in the whole, wide world really don't know that much. - Mose Allison
if the js code is compiled to your native code, it won't run too slow.
There is a spark in every single flame bait point.
Except that people can easily buy enough power to satisfy their needs for a small premimum on top of what a terminal costs. Look at around at the so called thin-clients available. Even the thinnest of them has enough power to be a "fat-client" with substantial processing power.
Add on top of that people have routinely rejected thin-clients. Bandwidth and latency are big problems. I expect acess to my files and data with low latency. That means viewing my 8MB digital photos without waiting for part of all of it to come over a wire. I expect it to be available to me all the time.
Google is great, but Google is not above the law of physics. People - just average users - have 20 or 30 or 40 or 80 gb of data on their PCs. No matter how great Google gets, providing this amount of data quickly, securely, with low latency and high-availablity will prove out of reach. Even with Google's highly skilled team of programmers, making a decently response web-mail client, or map tool is a pain in the ass. And it's still below par. Despite how great Gmail is, it's not nearly a rich as Thunderbird or Outlook 2003.
Latency
-- I was raised on the command line, bitch
Since when are we happy about monopolies in the making? Google is cool now, but can we trust them to stay that way indefinitely?
Well, it's not done yet and they still have competition, but I'd feel a lot better if these next generation things that are supposed to be used by the whole internet community were open and democratic like Wikipedia and not close and proprietary - however cool they are - like Google.
Treehugger? Treehugger... Treehugger!
Games can never have enough resources, at least for 3D games. It all comes down to the best visualization and how smooth of a frame rate you can obtain that will in turn provide the best experience. If and when google will provide the brute force CPU and GPU cycles needed to run Doom3 smoothly via dumb terminal, let me know. Until then, there is a reason the latest and greatest video cards are so damn expensive. And I REALLY doubt google want's to foot the bill for gamers and their never-ending quest for a newer and better visual experience.
Life is not for the lazy.
I don't agree.
By publishing your website, you are granting an (implied) licence to the world to create cached copies of the website. Were this not the case, your web browser's cache and your ISP's proxy server's cache would in constant copyright violation.
The argument Google would use is that they're just going a step further in having a publicly available cache. Whether the implied licence extends to this is arguable: I have no special knowledge of US law but under English copyright law they have a pretty good case.
>The DMCA specifically allows caching, so it's more in a gray area than blatent (sic!).
m ca_law_1998102 0_pl105-304.html
It allows cashing if the content is unchanged as in proxy server cache, not as in Google's permanent and modified cache.
See:
http://www.eff.org/IP/DMCA/hr2281_d
" the material described in paragraph (1) is transmitted to the subsequent users described in paragraph (1)(C) without modification to its content from the manner in which the material was transmitted from the person described in paragraph (1)(A);"
while this isnt the optimal choice for most people, it would be great for many. think about your parents.
my mom is 59. she uses email and the internet via AOL. she opens photo attachments and, maybe once a month, does something in word or excel. when her PC acts up, she doesnt know anything about fixing it, nor does she want to take the time to fix it. a thin client would be ideal for her.
on the subject of thin clients, dont write them off - i wouldnt be surprised to see office environments return to thin client setups. i am an admin for a 50 person central office with 80 remote locations who all connect to us via terminal services. all their apps are web based, and there are no privacy issues since this is all company property and all usage should be work related. i am single handedly able to successfully administer a nationwide network of over 80 locations for the simple reason that all of the big iron is right here next to me, and all of the clients can be replaced within 15 minutes.
Four-digit slashdot ID. Recognize.
Ellison was barking about "net computers" 10 years ago.
No one paid attention and for good reason. Why?
1. Bandwidth.
2. Storage Costs.
3. Computer costs.
1. Bandwidth
When the idiotic notion came up that broadband will kill the DVD, I responded here, noting that even in the middle of San Francisco, DSL is still painfully slow, and here it is, 2005. We're supposed to have jet packs by now, right? And TFA is talking about editing video over the web? Sure - in who's life time?
2. Storage Costs.
Continue to plummet. I remember when Ellison was barking about dumb terminals - RAM was extortionate. In '94 I bought a ONE GIGABYTE drive from HP for $580 and thought I'd gotten the deal of the decade. Now, for $80 less I can get a MiniMac and dozens of time more drive space PLUS a pile of RAM and processing power that totally smokes my creaky old Centris 650. I can now put on the end of my keychain what used to be a huge SCSI drive. Storage is no longer a problem.People not backing their stuff up is another issue, but it's not from lack of cheap drive space.
3. Computer Costs.
Which brings us to the cost of computers - I'm typing this on my old Blue and White G3 Yosemite. It's running in OS 9.2 and will do so as long as I own it. Why? Because it works. It has 80 gigs of drive space on three different drives - plenty of room for email and back up. I can do basic image editing in Photoshop 6, layout in FreeHand 9 or Quark 4, HTML editing in Dreamweaver 4, and ya know what? It fuckin' works. You can pick up a computer like this on eBay for next to nothing. What "Dumb Terminal" is going to compete with that? I saw someone dumping a perfectly good Dell P3 / 700 on the street last month - he was moving and couldn't give it away. I didn't want it - I already have my G3 / 350...
There is no economic incentive (as computers drive down in cost), there is no technical advantage (as storage drives down in cost) and, crucially: the bandwidth simply isn't there, period.
And won't be - for a very very long time.
Therefore: it's a dumb idea, it won't work, and it's as good as dead in the water.
TFA is full of crapola - typical techno-positivist day-dreaming nonsense - people who smoked the dotcon crack pipe and believed.
Idiots.
RS
Shoes for Industry. Shoes for the Dead.
Google's cache is available to the public. Anyone can use it, including their competitors. Thus it does not provide a commercial advantage to them.
Don't be so near-minded. Twenty years from now we might be laughing at statements like this as we download data over fiber-optic cables faster than current hard drive seek/read times.
By publishing your website, you are granting an (implied) licence to the world to create cached copies of the website. Were this not the case, your web browser's cache and your ISP's proxy server's cache would in constant copyright violation.
I disagree. There is no license implied there. You are allowed to make a cached copy on your own computer due to fair-use doctrine. You don't have or need a license to do that.
As for the ISP's proxy server cache, it may very well be in violation, as well as Google. But the truth here is that there is little motivation to do so because few are hostile to Google, and secondly it is easy to avoid being cached (or indexed).
You've got it to a certain extent. I think that this will not only apply to the Third world, but any company in the US. They can put Word Processing, E-Mail, Web browsing, and everything else into a central server. The server would be running an OS developed by Google. Then they could have a very simple "thin client" running on each person's desk. This would save the company a LOT of money, plus it would be easy to backup all the data because it would all be on one machine.
;-)
You know, adding a smiley doesn't absolve you of the responsibility for saying in your comment just *what the fuck it is*. Now that the link is dead, all we have are a bunch of comments saying "Wow, that's cool!", without any indication as to what the hell is so cool.