2 ms·
No. The straw man: "to tell everyone else all these static type checks are useless." The actual (from Uncle Bob's article): "Now I don’t want you to think th
by mpweiher 10y ago
No.
The straw man: "to tell everyone else all these static type checks are useless."
The actual (from Uncle Bob's article):
"Now I don’t want you to think that I’m opposed to statically typed languages. I’m not. There are definite advantages to both dynamic and static languages; and I happily use both kinds"
"useless" vs. "definite advantages"
Reading helps.
Oh, and obligatory reference to The Refactoring Browser[1] for the common fallacy repeated in the linked article that static typing is necessary for refactoring:
"We originally thought that the lack of static type-checking would make it hard to build a refactoring browser for Smalltalk. Lack of type information is a disadvantage, but the advantages of Smalltalk made it a lot easier to make a refactoring browser for Smalltalk than it would have have been for C++ or Java."
The first automated refactoring tool was created in a language without static type information, and it certainly was and maybe still is the gold standard for such tools.
Knowing your history also helps.
[1] http://wiki.c2.com/?RefactoringBrowser http://wiki.c2.com/?RefactoringBrowser