this post was submitted on 14 Jun 2023
26 points (100.0% liked)
Programming
568 readers
1 users here now
All things programming and coding related. Subcommunity of Technology.
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You may actually miss out when using an IDE. Driving without training wheels is more fun :)
I've used IDEs (Netbeans, Intellij) in the beginning but then started migrating away. They where just too heavy for me. Also, often IDEs do lots of stuff in the background such that you easily don't understand fully what is going on. Now I settled using the 'helix' text editor. It provides some IDE-like features like integration with language-servers, syntax highlighting, code completion, file navigation, code navigation, symbol search. But there are no dozens of buttons for triggering compilation etc. You do all this on a separate terminal.
Quite handy for such setups are tiling window-managers like i3. They allow you to easily fit the editor and terminals on the screen. This way you also don't need the build-in terminal of an IDE.
IDEs can automate build/test flows. But you can also automate them with scripts. This has the significant benefit that you can check this scripts into your version-control system (git) and publish them together with the code. Then your collaborators can use the exact same scripts. With IDEs that's really not working well because it would force others to use the same IDE as you. Possibly the IDE configuration is not even version-control friendly.