Live data from Hacker News

Google Open Sources Collaborative IDE

plus.google.com

31–40 of 54 posts

Re: Google Open Sources Collaborative IDE

#33

Doesn't Google only open source projects when they don't want to spend any more time working on them?

no, for example http://code.google.com/p/closure-compiler/ http://code.google.com/p/guava-libraries/ and http://code.google.com/p/protobuf/ are all active open source projects at Google, and there are many more.

Re: Google Open Sources Collaborative IDE

#34

At least it should allow one person selecting a block of text and make it also highlighted in the other one's window?

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!

Re: Google Open Sources Collaborative IDE

#35

/me reads features... Awesome! /me reads Java 7 requirement... Sadness.

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.

But yeah, Java7 on Mac is a pita :(.

Re: Google Open Sources Collaborative IDE

#37
post #24

Bigger news? After nearly 7 years, Google decided to shut down its Atlanta engineering efforts. That's a relatively old shop to shut down. Anybody know how big it was?

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.

Re: Google Open Sources Collaborative IDE

#38
post #24

Bigger news? After nearly 7 years, Google decided to shut down its Atlanta engineering efforts. That's a relatively old shop to shut down. Anybody know how big it was?

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…

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.

Re: Google Open Sources Collaborative IDE

#40
post #24

Bigger news? After nearly 7 years, Google decided to shut down its Atlanta engineering efforts. That's a relatively old shop to shut down. Anybody know how big it was?

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…

[deleted]
Post reply on HN