Looking at the svn repo ( http://goosh.googlecode.com ) this project is over 2 years old.
The unofficial Google shell
21–30 of 56 posts
Re: The unofficial Google shell
#22http://news.ycombinator.com/item?id=1025039
Here's how I see reposts. I agree that people shouldn't just repost things because they were popular at one point, and they want the karma. However, realize that for people who weren't around when that was posted (over a year ago), this is pretty cool. There is also no way I would have ever thought "Hey, I wonder if there is a shell-esque interface to google? Oh, I bet HN will have a link about it! Let me go search!"…
edit: emphasized what kind of stuff in /new
Re: The unofficial Google shell
#23There has to be a few easer eggs.
Re: The unofficial Google shell
#24Re: The unofficial Google shell
#25http://news.ycombinator.com/item?id=1025039
Here's how I see reposts. I agree that people shouldn't just repost things because they were popular at one point, and they want the karma. However, realize that for people who weren't around when that was posted (over a year ago), this is pretty cool. There is also no way I would have ever thought "Hey, I wonder if there is a shell-esque interface to google? Oh, I bet HN will have a link about it! Let me go search!"…
Re: The unofficial Google shell
#26http://code.google.com/p/googlecl/
I was blown away the first time I edited Google doc using vim, hit ":wq" (save), and saw my changes reflected instantly in my browser, where I had opened the same document.
The Oauth authentication was also pretty cool. Instead of asking for your Google credentials every time / saving them on your machine, the first GoogleCL use opens a browser window, prompts you to log into your Google Account, and asks you to authorize the Google CL client. You may then revoke this permission at any time (like any Oauth token).
Re: The unofficial Google shell
#27Re: The unofficial Google shell
#28Re: The unofficial Google shell
#29Re: The unofficial Google shell
#30Wow I've been thinking of writing something very similar lately using nodejs and parsing the html (maybe using lynx --dump). But this is pretty much as good idea and blazing fast!