I can't speak to the details of the decision. But what I can say is that aside from canning our site, Google treated us pretty darn well. We were all offered relocation options to other Google offices, which would come with cost of living pay bumps, paid moving expenses, etc...
And they let us open source pieces of the thing we were working on. Pretty sweet.
Some stayed with the company. But unfortunately, many of us could not make the move to another eng site.
Thanks for the reply. Externally, watching Google kill of products is hard, but it's easy to forget that they might be killing off engineers with these moves too. It's great to hear that they're trying to keep the talent and just shed the real estate.
I've just recorded a short 3 minute screencast showing an install and demo of Collide: http://www.youtube.com/watch?v=8Gq12bLbm54 - to just see what it looks like in action, jump to 1:45.
(Please note, I have no special connection to the project.. just saw it here this evening, installed it, and poked around slightly ;-))
Thanks, I might! I hate tools and mechanisms like this for my normal work, but for recording screencasts within 1280x720 it seems like it could speed things up a lot.
Can you explain this in a little more detail, or have a blog post about it? I've been thinking about doing something similar (`screen` for shared coding environment, with some other thing -- skype, say-- for video chat). I'd be very interested to know details about such a set up someone else has used, and any caveats or issues (for instance, screen didn't seem to export the environment faithfully, in my limited experience).
I have done remote pair programming with screen for a long time. Tmux might be more modern, but I have never tried it.
Caveat with using screen: You must suid root the screen binary, which is not very cool.
Put the following in .screenrc:
multiuser on
acladd <other username>
Then, start a screen, and the other user can join it using:
screen -x <your username>/
The slash at the end is important.
I like to add some stuff to the screenrc setting up a status bar at the bottom showing all the windows and which users are viewing which window, but I'd have to dig out my old screenrc to remember how.
Skype for audio chat, or some other audio chat (even just a phone call which is what we did a lot back in the day) is essential. Video is less important and hogs a lot of bandwidth.
Good luck, I really hope collaborative remote programming becomes more popular!
I have used GNU Screen + Skype in the past as well and it worked out quite well.
"I like to add some stuff to the screenrc setting up a status bar at the bottom showing all the windows and which users are viewing which window, but I'd have to dig out my old screenrc to remember how."
Or you could use Byobu(https://launchpad.net/byobu) which is an enhancement of GNU Screen and comes with a lot of good features.
We decided to have a little fun with the open sourcing and play with some cool new open source tech for a change :).
I settled on vert.x (the server container that requires Java 7) because it seemed to have a lot of affordances out of the box for client-server transport, and it's architecture made it easy to port/re-build pieces of our server stack.
If you're complaining about the memory usage, lower the max heap size with the arguments: -Xms512m -Xmx512m. If it's CPU usage: turn off some of those addons. You can't say Java 7 is the root cause of the CPU usage and not Eclipse.
Not really. "It doesn't really use any parts of Wave's collab stack...We only really use the Keyboard signal event stuff from Wave since it is a pretty great library" -Jamie Yap's comment on g+ post.
Apache Wave is alive and well. BTW, I think we can stop calling it Google Wave :-)
I run Apache Wave on my laptop just to kick the tires and I had it on a server for a while so I could ask a few people to try it with me. It is an instant install and run from either the svn or mirrored git repo, if you use the default file store. Configuring it with MongoDB as a data store takes some more effort.
I'm pretty excited about the new wave of IDE's in the browser: Cloud9, Eclipse Orion, and Collide. Just having them available, with my last setup, from any computer with an internet connection and a browser makes my life easier. Collide looks like it's using one of the internet's big plusses: collaboration. Kudos and keep going.
EDIT: grammar
Collaborative cursors and selection highlighting broke during the open sourcing. What we released contains a ton of brand new code since we essentially had to build from scratch a one-off local server to drive the parts of the client that it made sense to release.
Code churned a bit :).
I have it on my list to get that working again soon!
"The Collide .. is a technology/library release, with a basic reference implementation provided out of the box. It is not a hosted service, or any kind of product competing with existing web IDEs like Exo or Cloud9.
...
These existing web-IDE services could leverage technology in the Collide stack."
So we will definitely try to integrate Collide's collaborative coding abilities into eXo's http://cloud-ide.com ASAP
Hopefully it should not be as complex as cloud-ide uses pretty the same stack of things (GWT, CodeMirror etc), so stay tuned :)
