Leaving aside any license compatibility issues, an open source project with a proprietary dependency will lose users compared to an open source project with entirely open dependencies. This also causes problems for some Linux distributions.
I've been an OSS user and contributor since the middle 1990s and I very much welcome these moves. SaaS has been getting a free (in the unfair sense) ride without contributing in any way.
Furthermore, the presumption that users of the software are now required to contribute back flies in the face of the agreement.
I'm not against people using a license like this. It does however seems a slap in the face to change the license after benefiting from the fact that you are releasing an open source product.
tl;dr: It's a bait and switch, and dislike it.
[0] https://github.com/cockroachdb/cockroach/graphs/contributors
No, that's exactly what we are talking about. The threat of big cloud players swallowing up the SaaS model that powered opensource to the current highs, is very real. Until Amazon and friends were mostly interested in powering the low-level bits, it wasn't a big deal; but now they are moving up the stack and pulverizing the small businesses that drive the OSS ecosystem. That is a problem.
The AGPL was supposed to protect against this sort of play and it really isn't, for various reasons. Personally, I welcome the attempts at innovating in this area particularly when they are clearly well-intentioned like this one.
> I'd hate to see a project I contributed to change it's license to something that limits how the applications can be used
Unless you've waived your rights, you can exert your copyright and block any such move.
Should have thought about it beforehand.