There are arguments to be made for both dynamic and static languages being good for moving quickly or accommodating change, often in the context of a startup. And it's true for both, except that a static language only lets you move quickly between correct programs.
-
Show this thread
-
Replying to @propensive
I would say programs which don't crash. But no crashing and correctness are different things. You can have bulletproof program which works badly and has invalid logic implemented. Such program is not correct.
2 replies 0 retweets 0 likes -
Replying to @macsikora
Sorry, I was using the specific meaning of "correctness" of "correct with respect to its specification" and that specification is given by the types. That's basically what you described as "doesn't crash". It says nothing about correctness with respect to the customer's intent.
1 reply 0 retweets 1 like -
Replying to @propensive @macsikora
Can a dynamic program be both intent correct and spec incorrect?
1 reply 0 retweets 0 likes
Only if the spec doesn't reflect intent, I suppose...
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.