4 ms·
Should they just not implement the feature at all, or would you like them to pay for it? I don't understand what the exact problem is you're having.
by Timon3 3y ago
Should they just not implement the feature at all, or would you like them to pay for it?
I don't understand what the exact problem is you're having.
- ilrwbwrkhv 3y agoI should get all features once I pay for the IDE. Either they shouldn't add the feature or pay for it themselves.
- Timon3 3y agoBut it's literally a feature that creates ongoing cost based on usage. Why must you either get it for free, or not have it in the IDE at all? Why can't they implement it for people who want to use it, and you continue not using it (since it's impossible for them to finance with the existing licensing model)? I could understand your point of view if it was a feature that could be made free in some way. But it literally can't - so you just don't want others do have this feature, because you can't have it for free. Why?
- moqmar 3y agoI think it should come as a promoted extension or something, there are just many users who can't or won't use this feature due to it requiring a contract with a third party. Shipping it with the IDE itself unneccessarily bloats it and probably slows things down.
- Timon3 3y agoIf you can show a negative impact from this feature when disabled I'll agree with you. Until then I'll assume it doesn't have a negative impact (like other IntelliJ features I don't use).