4 ms·
Emacs is not a python oriented IDE. So the comparison is moot from the beginning. Some people likes what Emacs offers and mesh it with external tools. Some pref
by skydhash 1y ago
Emacs is not a python oriented IDE. So the comparison is moot from the beginning. Some people likes what Emacs offers and mesh it with external tools. Some prefers a more complete package. Nothing wrong with either, especially if you have the time and the knowledge to iterate quicly on the first.
What you may need is something others can do without. So what’s best is always subjective.
- LeafItAlone 1y agoSure. I think it’s odd for you to criticize someone’s reasons when you apparently just reject their underlying premise to begin with (which is, effectively, my experience with a particular open source tool isn’t the best for me and the one I found that does isn’t open source). Frankly, the idea of having 4 different ways of editing code, as you’ve described above, just seems like a nightmare to me. I like to have one tool that does it all and learn to use that tool well. The Jetbrains tooling allows me to do this with little of my time spent configuring it. If what you are using works well for you, then I think we should all be happy here.
- skydhash 1y agoThe point I was making was against conflating optimizing tooling and wasting time not solving problems. Not about going with an IDE or not. Everyone works differently. For most tasks, I prefer Emacs. But for pairing, VS code may be more familiar to others. And it’s hard to get rid of Android Studio and XCode if you’re doing mobile development. No one can judge workflow and tooling choices as long as the results are in.