4 ms·
Chrome vs. Zapier is an unfair comparison. Chrome is ~6.7 million lines of code and takes hours to build while Zapier is probably a microsevice architecture an
by kowdermeister 8y ago
Chrome vs. Zapier is an unfair comparison. Chrome is ~6.7 million lines of code and takes hours to build while Zapier is probably a microsevice architecture and is easier to update a component / validate an issue.
- busterarm 8y agoI'm not _just_ talking about Chrome. I think that you would be hard-pressed to find any Google product where you'll find a responsive support channel.
- nojvek 8y agoHaving humans doing customer service is not something google will ever do well. It’s not in their DNA. They are all about solving big problems with fancy algorithms. There is a reason Google keeps on making failed social networking products and a 100 messaging apps. They are far more interested in algorithms that can scale than messy little customer issues. The problem is that you can’t deliver great customer service with algorithms just yet.
- tech_tuna 8y agoCouldn't agree with you more. Google is not a people-company.
- juancampa 8y agoYet Google is very successful
- tech_tuna 8y agoAt selling ads.
- cannonedhamster 8y agoHad a major DNS bug with Google DNS, it was on their side and they were completely messing up how they were handling some requests. Took them 2 months or so to fix it, they never described what happened, never said what was broken, and it took finding resources inside the company to solve. Google doesn't functionally have support for many of their paying services, nevermind their non-paid services.
- ovi256 8y agoSo what you're saying is microservices for desktop apps, right ?
- jashmatthews 8y ago> Zapier is a monolithic application built on Python and Django. https://zapier.com/engineering/go-no-go/ https://zapier.com/engineering/go-no-go/