3 ms·
I'm not sure, but given the intermittent grief I've had with this, it seems like they have to pay a team to maintain it. Maybe it's more than just some cheapo s
by jfengel 5y ago
I'm not sure, but given the intermittent grief I've had with this, it seems like they have to pay a team to maintain it. Maybe it's more than just some cheapo storage and CPU time, but a cost to them in maintenance (including unexpected upkeep of seemingly unrelated features).
I can't imagine why that is. You'd think it would be easy. But I've had enough cases where my account wasn't compatible with something (especially my Pixel phone) that makes me suspect that this lets them jettison some of their code base.
- bener 5y agoWouldn't it be running on the same setup as their paid offerings? It's the same thing, just with limitations.
- jfengel 5y agoIt's the limitations that cost money. They are code and might require maintenance. It doesn't seem like it would, but I have found myself in plenty of situations where I couldn't give an "easy" feature or fix an "easy" bug because of some design choice that was riddled throughout the code. No idea what it might be, but I could take guesees. The maintenance cost is probably small for them, but not to support a customer paying zero.
- sschueller 5y agoThey are migrating everyone to the same system as the paid one and deferring payment for a month. So to me it sounds like a flag.
- labster 5y agoIt sounds to me like a false flag. Free for life*! (* mayfly lifetime) Time to degoogle my life. Google giveth and Google taketh, and Google discontinueth after years twain or so.
- frosted-flakes 5y agoIt's been a lot more than two years though, it's closer to 15.
- Aloha 5y agoI 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 ;-)
- sangnoir 5y ago> I have run without support for 14 years, I take about as much resources for them as a gmail account. 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.
- compsciphd 5y agoExcept, they might be sued now, and it might be significantly more expensive. They probably forgot what they wrote in their blog post http://googlepress.blogspot.com/2006/08/google-launches-hosted-communications_28.html http://googlepress.blogspot.com/2006/08/google-launches-host... "Furthermore, organizations that sign up during the beta period will not ever have to pay for users accepted during that period (provided Google continues to offer the service)." Yes, they can claim they are no longer providing the service, but that's difficult to argue when they are providing a functionally identical service that is just a billing change to cause a "migration".
- GauntletWizard 5y agoHaving been the administrator for these, there was real cost to maintaining all the weird SKUs that Google Apps for Your Domain (which dates when this was) had at the time. It was not unthoughtof, but it also wasn't huge - and this SKU was not among the problem SKUs.