> I'm not talking about this feature exclusively. Well that's weird because: a) Everyone else is b) You definitely seem to be talking about it and specifical

> I'm not talking about this feature exclusively. Well that's weird because: a) Everyone else is b) You definitely seem to be talking about it and specifically have targeted your comment to this feature in the comments section about this feature So it feels a bit weird to now say "it's not about this feature"... > there's a lot of incentive f We can sum up virtually all of your post as "something in the future could be bad". OK, yes, something in the future could be bad. That is always true. > large corporations JetBrains isn't even VC funded, they're a privately owned and profitable company. Comparing them to Microsoft without addressing this feels disengenous. > an't see the downsides if a critical mass of users accept the changes. I mean, I think it's ridiculous to go "look at how JetBrains is changing" in a thread where everyone has misunderstood a minor bug that in no way indicates that JetBrains is changing. They're adding services, wow how awful. > Except Jetbrains is about to get their first taste of what it's like to have some of their customers dependent on a feature that isn't available locally. No one depends on this. Your IDE starts up fine without it. You don't need it. You can use a competing plugin (they already exist) that runs locally or in some other service. > If it's seen as a financial success, do you think they'll be able to resist the temptation to start moving everything they can to cloud connected features? I think it would be a ridiculous move for them to completely change their core business model to be exclusively service oriented, yes.