9 ms·
I enjoyed dumping on Google earlier too. I love firebase, but I've talked two companies I've worked with out of using it for new, mission critical projects. The
by josephg 10y ago
I enjoyed dumping on Google earlier too. I love firebase, but I've talked two companies I've worked with out of using it for new, mission critical projects. The earlier article made me feel completely vindicated in my recommendations.
I simply have no trust that:
- Google won't randomly cancel firebase (wave, reader, etc)
- Google won't randomly, suddenly jack up the prices for firebase, leaving users in the lurch (appengine)
- When something mission critical breaks or changes, I'll have any way of contacting someone who cares, no matter how much my company is paying for the service. (Google's support forums are a pit of sorrow)
I was reading an article the other day talking about personhood[1]. It makes the point that part of being a member of society is the idea of standing. That is, if you break your word there has to be a way for you to lose out as a result. If there isn't, its impossible for anyone to enter into an agreement with you because you can't be trusted. Forming an agreement requires both sides to have skin in the game.
I don't genuinely believe that google has skin in the game when it comes to cloud services for small-to-medium customers. Its just too easy for them to drop the ball, stop answering emails and leave customers in the lurch. They've done it again and again. I'd say its the default way Google operates.
Thomas Schelling from The Strategy of Conflict:
> Among the legal privileges of corporations, two that are mentioned in textbooks are the right to sue and the "right" to be sued. Who wants to be sued! But the right to be sued is the power to make a promise: to borrow money, to enter a contract, to do business with someone who might be damaged. If suit does arise, the "right" seems a liability in retrospect; beforehand it was a prerequisite to doing business.
Please, firebase. Please be different. But know that thats the reputation you're fighting against. Thats the reputation you've inherited by joining Google. But for now I'm standing by my earlier recommendations.
[1] http://www.meltingasphalt.com/personhood-a-game-for-two-or-more-players/ http://www.meltingasphalt.com/personhood-a-game-for-two-or-m...
- teddyh 10y agoAs I said two years ago¹, Google is too large to have actual customers, per se, since any group of paying users is still too small for Google to need to pay attention to. ① https://news.ycombinator.com/item?id=9912754 https://news.ycombinator.com/item?id=9912754
- paulddraper 10y agoThese are all little hobby projects for the advertising company.
- crypto5 10y agoPart of ecosystem. See how firebase today is integrated with analytics/ads.
- user5994461 10y agoBullshit. Any telco operator has millions of customers and it handles support just fine. Any bank has millions of customers and it does support just fine. Google enterprise products (Cloud, app engine, apps) are nowhere near that number. They have no excuse for not having support.
- nikanj 10y agoYou must be living with different telcos and banks than the rest of us. They often frequent the lists of most hated companies, for example [1] has good representation from both industries. [1] https://finance.yahoo.com/news/america-most-hated-companies-110032495.html https://finance.yahoo.com/news/america-most-hated-companies-...
- user5994461 10y agoI don't have much to complain about all the providers I had in my life. Sure, I had to wait 15 minutes on the phone a few times, or send letters now and then. Nothing out of the ordinary.
- teddyh 10y agoI think you misunderstand me. I’m not saying Google couldn’t have acceptable support. I’m saying they don’t have to; there is simply no perceptible downside to them if they don’t.
- 10y ago
- victorhooi 10y agoI think you've mischaracterised things a bit in your post - not sure if this is just because you're repeating what you read elsewhere? Anyhow, regarding the bullet points: 1. Google Wave was released an experimental consumer product, designed to combine the best of IM and email. According to the announcement, it was finally sunset due to lack of interest from the public. Personally, I was super excited about Wave - I even pestered an ex-Googler at the time to get me in on the preview. (I was in uni at the time). However, I had a lot of trouble getting other people to use it. Did you personally use Wave yourself? Were you able to convert anybody else to using it? Firstly - this is hardly apples to oranges. You're comparing a experimental consumer-oriented preview product, to an enterprise offering with SLAs. It would be like if we released a Star Wars game showcasing awesome new WebGL features - then decided to sunset it 12 months later. Secondly - the project was open-sourced and then moved to under the Apache banner - an effort that in itself took significant engineering effort. https://en.wikipedia.org/wiki/Apache_Wave https://en.wikipedia.org/wiki/Apache_Wave I'm not really sure what more you want? In the case of Reader - this is somewhat personal, as I was a big lover of Google Reader as well. From memory, it was deprecated with around 12 months of notice, there were provisions for migrating/exporting all your data etc. It wasn't open-sourced like Wave, but there were reasons behind that (I can't comment). However, it was hardly the worst handled deprecation - and to be honest, the writing was on the wall for RSS for a long time before that. 2. You didn't provide any specifics, so I'm not sure what event you're referring to. AFAIK, the only major price change was when Google AppEngine left beta/preview, and became an actual commercial product, and Google added SLAs, and other things etc: https://groups.google.com/d/msg/google-appengine/Hluog1_a3n4/uFMhaBWhVi8J https://groups.google.com/d/msg/google-appengine/Hluog1_a3n4... The changes were announced at I/O that year (May), I believe, and the actual changes took effect in September. Is that what you're referring to? Because even taken aside my Google hat, that seems like a fairly reasonable thing to do. 3. All of Google's enterprise offerings have support. I know, because I actually work in such a support team. For GSuite, support comes free as part of the product - you can contact us via email/chat or over the phone. For GCP, there are commercial support packages available (https://cloud.google.com/support/ https://cloud.google.com/support/) (similar to the AWS model). > They've done it again and again. I'd say its the default way Google operates. This is a pretty bold claim - can you cite any examples of this? If this is something that personally affected you - please feel free to reach out to me. I can't promise I can fix everything, but I can definitely try to find out more for you, or see what I can do internally. Disclaimer: I work for Google, but views expressed above are my own.