Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tables: Tracking work for teams

blog.google

Post reply on HN
Print view View original

201–210 of 375 posts

Re: Tables: Tracking work for teams

#201

Post by alasdair_ »

ithkuil wrote: post #190
xkcd-sucks wrote: post #176

Earlier quoted context omitted.

Is it even remotely possible that Google would sell discontinued products to other entities, e.g. raise money to buy Wave as a separate company or something like that?

Not as long as products are built on top of proprietary internal SDKs such as google3, borg etc. Google started to open source some of the internal projects (e.g. bazel), which, among other things, would make it easier to just donate / spin off a project they are no longer interested supporting.

I worked at a Google spinoff a few years ago. It took a lot of work to move everything from internal Google infrastructure to external (Google Cloud) and it probably took a full year after the official date of us leaving Google to have everything fully migrated - there were lots of small things like seldom used config files or occasional scripts that still relied on Google’s internal stuff.

Re: Tables: Tracking work for teams

#203

Post by pc86 »

toomuchtodo wrote: post #148
prlambert wrote: post #76

Earlier quoted context omitted.

[Disclosure I work at Google Area 120 and would be partly responsible for this type of decision] This is a really helpful comment and I like the nod to transparency. Thank you! Not sure we could get quite so concrete publicly (there are lots of unknowns and wouldn't want to make commitments we can't keep), but aligning goals between the business, team, and users/customers is a great idea and something we can improve…

Could Google not commit to open sourcing projects in a maintainable way (public repos, k8s support versus just Borg, which no one has access to) and guarantee data export functionality as part of Takeout? This would significantly derisk attempting to use a fledgling Google service for end users. Definitely not a resourcing issue, entirely an organizational culture and philosophy decision to be made.

I don't work at Google but my understanding is there are a lot of proprietary, closed-source internal APIs that make this difficult-bordering-impossible.

Re: Tables: Tracking work for teams

#204

Post by naringas »

samblr wrote: post #174
tmd83 wrote: post #73

Does anyone feels looking at Google's products lately that there's something tremendously wrong with the organization. I'm not talking about just dropping features but just quality of implementation and missing things that people should get fed up and do something during development. Like hangout > chat, let's drop the existing feature of read receipt that is even more important in the remote/work world in a product…

Let's admit it. Google is on its way to become the new ____. IBM ?

they are quite a lot like Microsoft of the late 90s and early 00s

Re: Tables: Tracking work for teams

#206

Post by heavyset_go »

bram2w wrote: post #123

I see a lot of comments about people who are worried that Google might shutdown the service entirely and I agree with your concerns. The last months we have seen a lot of giants building their own database spreadsheet like hybrid, Google Tables, Microsoft Lists and Amazon Honeycode. Tools like these contain your most important data and you want to have freedom, security and independence as they can be an important pa…

This is pretty cool, thanks!

Re: Tables: Tracking work for teams

#207

Post by ponker »

ithkuil wrote: post #190
xkcd-sucks wrote: post #176

Earlier quoted context omitted.

Is it even remotely possible that Google would sell discontinued products to other entities, e.g. raise money to buy Wave as a separate company or something like that?

Not as long as products are built on top of proprietary internal SDKs such as google3, borg etc. Google started to open source some of the internal projects (e.g. bazel), which, among other things, would make it easier to just donate / spin off a project they are no longer interested supporting.

Also a failed product from Google will be worth no more than $1 billion which is hard to get the Google C-suite excited about.

Re: Tables: Tracking work for teams

#208

Post by lowiqengineer »

cflewis wrote: post #178
someone7x wrote: post #97

Earlier quoted context omitted.

Are all these comments about the near and inevitable death of your new product at all soul-crushing? I'm a stranger on the internet and even I can feel the burn. Good luck.

As a Googler, I'd just say it's a boring meme that shows little thought and just wastes time actually getting to interesting discussion here. It's almost akin to "first" from the old days of Slashdot or the race to mention generics whenever anything related to Go comes up. Products come and products go, this is not unique to Google. Killed By Google is cited as some sort of proof, but that goes back to _2003_, and do…

Really not helping the condescending Googler stereotype there bud. Or perhaps its OK for you to be this way as a tech "elite" that makes $450k a year.
Post reply on HN