|
|
|
|
|
by Aloha
1616 days ago
|
|
I have run without support for 14 years, I take about as much resources for them as a gmail account. Move me to the paid version, don't charge me, and then change me 50 bucks every time I need to open up a support case. But for 50 bucks, I had better be able to get an actual person on the telephone ;-) |
|
It's may not be about supporting you as a user,but about supporting the feature of a free-tier of features whose users are >99.9% paying customers. I imagine having to pepper "is_billable() && !is_grandfathered()" everywhere gets old, and leads to some subtle bugs/test failures for a feature that's used by 0.03% (a guess) of users, who also happen to be non-paying.
Additionally, at Google's scale, systems interact with each other in non-trivial ways. As a hypothetical, if the CEO/director decrees that all teams should use G-Pay's code & internal infrastructure for all payments (for compliance reasons) by 2023, that may necessitate code & schema changes that do not work with "(mostly) billable customers" because grandfathered accounts may not have a billing method available (which G-Pay systems require); the G-Pay team can't add support for the "billable-customer-but-not-really" feature until the second half of 2024, unless the Workspaces team can just removing an item from the 2022 G-Pay roadmap that's projected to bring in an additional $200M revenue p.a.
Disclaimer: I'm not a Googler, I'm speculating based on my experience in large organizations with intricate cross-dependencies. The Workspace engineers may empathize with you, but their hands are tied,and they can't publicly share the trade-offs that are being made, which is unfortunate.