3 ms·
> [change is] trivial. I just do it, and the compiler goes You are talking about the ability to refactor. In my experience with major refactors, you need a te
by mpweiher 8y ago
> [change is] trivial. I just do it, and the compiler goes
You are talking about the ability to refactor. In my experience with major refactors, you need a test suite, not the type checker. Why so specific? Very simple, when I did this in the past, the compiler tended to be happy way, waaaaayyyy before the test suite. Had I relied on just the compiler, I would have been in a very bad place.
> "locking down" an architecture
Simple refactors are not "changing the architecture". Static type systems tend to be fairly specific about the kinds of architectures that are expressible, and they tend to be "you can have any architecture you like, as long is it's black, er, call-and-return". Now we tend not to notice this, because we are so used to everything being call-and-return that we don't even notice it.
"We Don’t Know Who Discovered Water, But We Know It Wasn’t a Fish" -- Marshall McLuhan
Once you do notice, and you do want to build alternative architectures, the straight-jacked becomes very constricting.