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.
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.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.