IDEs or text editors are just tools in my tool box.
I use the tool that I consider suitable for my task at that time.
If I want to edit my Linux configuration I usually use simple editor like nano or vim because they always available and can be used through ssh.
When I'm creating Java project, I'm using IDEs like IntelliJ or Netbeans, because I can directly start to code without having to configure the build system.
For R project I also use IDE (RStudio).
I'm very comfortable using VSCode or Atom for web app projects.
Just pick the one that you feel comfortable with and suitable for your task.
What should I do if I disagree with the best tool for some of the jobs?
For example, doing JS/TS for web frontend projects is much better and more efficient in IntelliJ/Webstorm. But you have to break community guidelines concerning the import structure because you don’t manually manage imports/exports anymore and you let the tool do it for you (just like in Java/Kotlin, imports just happen automatically).
I mean, I really cringe when I see people crafting their export * from './somefile.js' inside of index.js inside of the package directory, so that it is available under a cute import, that will be easier to manage manually later.
Time wasting.
I don’t have to spend time on that whatsoever. Just create a bunch of JS files grouped into package/directories and never use export .. from .. construct, and never use default export.
That is of course when I write apps. With libraries the story is different.
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.
IDEs or text editors are just tools in my tool box.
I use the tool that I consider suitable for my task at that time.
If I want to edit my Linux configuration I usually use simple editor like nano or vim because they always available and can be used through ssh.
When I'm creating Java project, I'm using IDEs like IntelliJ or Netbeans, because I can directly start to code without having to configure the build system.
For R project I also use IDE (RStudio).
I'm very comfortable using VSCode or Atom for web app projects.
Just pick the one that you feel comfortable with and suitable for your task.
I agree so much with your comment.
What should I do if I disagree with the best tool for some of the jobs?
For example, doing JS/TS for web frontend projects is much better and more efficient in IntelliJ/Webstorm. But you have to break community guidelines concerning the import structure because you don’t manually manage imports/exports anymore and you let the tool do it for you (just like in Java/Kotlin, imports just happen automatically).
I mean, I really cringe when I see people crafting their
export * from './somefile.js'inside ofindex.jsinside of the package directory, so that it is available under a cute import, that will be easier to manage manually later.Time wasting.
I don’t have to spend time on that whatsoever. Just create a bunch of JS files grouped into package/directories and never use
export .. from ..construct, and never use default export.That is of course when I write apps. With libraries the story is different.