Perhaps it just has to do with modern practices and libraries encouraged by modern IDEs. I approached it recently, so I can't speak for times before the IDEs were there.
Strong typing is certainly very helpful for making smart compilers and tools---I can't deny that, I'm a Haskell junky. I don't think it's always a best practice though. Being able to handle horrible codebases means that the language/editor environment also allows horrible codebases to survive longer.
That always seemed a really, really unproductive notion to me, that great tools must be bad because they help you deal with problems that would otherwise make you fail sooner.
I didn't say IDEs weren't powerful or good in and of themselves. I indicated the opposite. Sports cars are fantastic. They are really fun to drive. I would start walking if everyone in America had one. Too dangerous.
I didn't say IDEs weren't powerful or bad. I indicated the opposite. Sports cars are fantastic. They are really fun to drive. I would start walking if everyone in America had one. Too dangerous.
Strong typing is certainly very helpful for making smart compilers and tools---I can't deny that, I'm a Haskell junky. I don't think it's always a best practice though. Being able to handle horrible codebases means that the language/editor environment also allows horrible codebases to survive longer.