4 ms·
I get where you're coming from, but relying on an IDE for safety is a recipe for disaster. What happens when you just quickly pop open that file in on a shell
by mi100hael 10y ago
I get where you're coming from, but relying on an IDE for safety is a recipe for disaster. What happens when you just quickly pop open that file in on a shell to make a small change and fat-finger something? What happens when a different developer decides to use vim for everything? I used Python extensively for years and it's still my scripting language of choice, but to use it to build something safe in a business-critical situation requires an obnoxious number of tests, half of which are basically just type checks.
- lowmagnet 10y ago1) you get an error, and since it's a small change I'd assume you could guess where you caused it. 2) they get errors but they may have more difficulty finding them. (or they use a vim plugin for that, or pylint, etc. on save) I'd guess your ability to suss out an error's cause without an IDE is a matter of comfort with a language, and your lack of ability isn't an IDE's fault.