This is very well reasoned and I mostly agree, but the reality is that if it was closed source it would be the same except you just couldn’t fix it yourself rea

This is very well reasoned and I mostly agree, but the reality is that if it was closed source it would be the same except you just couldn’t fix it yourself reasonably and legally. Google may be falling on its maintenance, but stuff like this crops up in proprietary software constantly. Presumably their calculus for putting resources on fixing your bug is just tilted against you. I think the cost of fixing this bug should be something that you consider part of the cost of using the service; no less than the cost spent maintaining or operating your own services should count when comparing the cost of self-hosting FLOSS stacks. Tl;dr: I think open source is still just a straight improvement here. I think it’s fine as long as the cost of fixing it is considered the cost of using the stack for decision making purposes.