So they killed Google code to... launch another code hosting thing?
Does Google have too many siloed product managers? Maybe you can only advance up the corporate ladder by releasing new products, and fuck all if they get killed later, because you got your promotion?
No clue what the cause. Just seems weird looking on from the sidelines.
After just wasting the last three nights migrating my old project (code was on GitHub, but the rest wasn't) off of Google code the chance of me putting code on a Google hosting service any time soon is pretty much zero.
About once a year for the last several years I have spent a few hours/days migrating stuff off of Google because the project is being shut down. Maybe they are just cleaning house from the mass of project in 2005-2010, but the constant reminder that the stuff I create is in danger if it lives on Google's servers is probably not the lesson they want to be teaching me.
Google code was project hosting, not just source hosting. This clickbait article is talking about a Google product that just does source hosting and is a part of the overall Google public cloud product strategy.
A while ago I remember hearing in some podcast from googler that they internally have separate source code management system (not related to Google Code). I wouldn't be surprised it he was talking about this one and they finally decided to make it public. Killing Google Code was probably just because not many people used it (externally or internally).
Does Google have too many siloed product managers? Maybe you can only advance up the corporate ladder by releasing new products, and fuck all if they get killed later, because you got your promotion?
No clue what the cause. Just seems weird looking on from the sidelines.