3 ms·
My usual development environment for is a Macbook Pro with six terminal windows open. The first one (Command-1 shortcut key) is a connection to the database, t
by ratsbane 17y ago
My usual development environment for is a Macbook Pro with six terminal windows open. The first one (Command-1 shortcut key) is a connection to the database, the second (command-2) is Vim with program code, the third (command-3) is library code or test scripts or whatever and the next three (smaller, with blue backgrounds) might be showing tail -f of Apache error or access logs or something like that. If I need to edit an image I command-tab to the GIMP, to view a web page, command-tab to Firefox or whatever. I can connect those windows to one or more remote boxes with ssh and not even have to think about what machine I'm working on. It's easy to reuse those windows for other things, close one with command-w or open new ones with command-n. Vim does syntax highlighting and will even auto-complete if I wanted to turn it on.
What would an IDE give me that this setup won't? To me, the setup I use IS an integrated development environment.
I have used Visual Studio, XCode, Eclipse, etc. but whenever I do I feel slow and inhibited because of the necessity of mouse movements (unless I want to learn a completely different set of key shortcuts that will only work in the IDE and not the OS) and the annoying tendency of IDEs to reformat my code or complete blocks I'm not ready to complete.
Also, OS X and Ubuntu both allow great control over terminal window transparencies and color schemes. I'm not aware of any other IDE that does. I like to keep my main editing windows at 70-80% transparent so I can watch logfiles/test scripts run in the background while I'm editing.