Exactly, and their target audience is developers, meaning they have even looser performance standards.
So how can you hope to be productive when you need to use those?
Don't you think this is kind of vicious circle, that need to be broken somehow?
In my opinion no, unless there is negligence. Companies providing tools should not prevent themselves to release features on the premise the users need a powerful machine (their is limit, yes but in general IDEs use resources decently).
Sure, it's a positive feedback loop. All I'm saying is they're acting rationally.
More rationally than boycotting them would be for those developers whose productivity in their job would be severely impacted by doing so.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Exactly, and their target audience is developers, meaning they have even looser performance standards.
So how can you hope to be productive when you need to use those?
Don't you think this is kind of vicious circle, that need to be broken somehow?
In my opinion no, unless there is negligence. Companies providing tools should not prevent themselves to release features on the premise the users need a powerful machine (their is limit, yes but in general IDEs use resources decently).
Sure, it's a positive feedback loop. All I'm saying is they're acting rationally.
More rationally than boycotting them would be for those developers whose productivity in their job would be severely impacted by doing so.