It is also an example of why I, as an end user, prefer FOSS licenses. The possibility of forking. The redistribution clauses there do not prevent forks, but definitely make them less likely, so you remain dependent on a single supplier.
The problem is that it creates a lot of uncertainty. For example, with this license, what usage is commercial? Can you distribute it to customers who buy other things from you? Can you offer services related to it - e.g. can you install it for a customer?
If you modify the software under what terms are your modifications distributed? Do they have to be distributed under the same terms? There is not transfer of copyright so the original authors cannot distribute the modified version commercially as part of their enterprise edition, that means that every modified version is a fork that cannot be merged back in?
As I said in another comment discouraging forks is a disadvantage for users as it leaves you dependant on one supplier.
The AGPL achieves the aim of deterring the likes of Amazon from providing the software as a service (at least without contributing their changes back, in practice the will not use it at all) without these sorts of problems.