In your post you talk briefly about licensing -- effectively (1) MIT/Apache are common and very permissive (2) AGPL sometimes gets shut down by legal (3) Changing licenses is hard.
Given these primitives, do you think one solution to the problem is just what we see here, a new licensing structure for some types of open source? Elastic's move here, attacking the issue through licensing, is one way that this sort of business model is becoming more robust over time and would be instructive for other founders looking to create revenue generating software that is also open source.
As a developer, the main reason I _love_ open source is that I help patch issues or inspect the code to get a better understanding. Which is great because the changes Elastic are making to their license are orthogonal to the value prop for your average developer.