this post was submitted on 01 Sep 2023
337 points (96.2% liked)
Programming
17373 readers
172 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Not arguing either side, but I'd love to hear your reasoning.
A linter a debugger and a clean interface in general are all I need. And most text editors suffice for that.
I've never been able to benefit from an IDE in a way that make up for how much slower and more bloated they are.
I'd love to hear what some of the main benefits are though.
Jetbrains IDEs do a lot of indexing and caching so that operations that normally take a bit are faster. Full text search, find usages, identifying interface usage in duck types, etc.
But the killer feature for me is the refactoring tools. Changing a function signature, extracting an interface, moving code to new files or packages, etc. I pair with folks who use VS Code and its a bit tedious watching them use find and replace for renaming things.
That does sound legit if you have resource limitations. Thankfully I've always worked for corporations that hand out MacBook Pros like candy. Normal day for me is having two Jetbrains IDEs open with Chrome, Slack, Zoom, and a dozen containers. Still runs smooth.
VS Code absolutely has refactoring built in. Pressing F2 on a token renames it everywhere it's referenced
Interesting. I'll have to find some docs and share it with my co-workers because they definitely don't use build-in refactoring. Thanks!