From the development side of the business, the more frequent release cycle has allowed the product teams to be much more responsive. Under the old model, with major updates every 18-24 months, I might receive a feature request which is implemented in a few weeks, but which the user doesn't have access to for a year or more. This was hugely frustrating as we want to make features and products our customers want to use, and to have it ready and waiting for so long was not a great experience for anyone. Now, we can have that feature in users hands in weeks or months.
I don't understand this idea that there will be reduced incentive to release updates under a subscription or membership model. If anything, frequency and responsiveness feels more important than before, and I don't know of anyone here who feels differently.
edit: I was more on the fence about subscriptions than unsupportive. It was a drastic change that required either gradual transition or a rip-off-the-bandaid approach.
It's almost impossible to keep mature products going without a subscription model. Mature products eventually only need:
a) support and b) compatibility/stability/performance updates.
But, these types of updates can be very expensive to develop and are very difficult to market as a new release (works with XXXX now isn't a very compelling proposition for upgrades).
It's kind of the same problem that open source software faces after it matures. Nobody wants to just sit and do support/incremental changes on old software, at least not for free.
I'm not particularly happy about moving to what is effectively a rent society, but I think this is one of the few silver linings of the subscription model.