Programming types and mindsets
-
One of the longest running schisms in programming is that of static vs dynamic typing. I've heard a million arguments from both sides throughout my entire career, but seen very few of them ever convinced anyone of anything.
Ruby with explicit, static typing would be like a salad with a scoop of ice cream.
-
One of the longest running schisms in programming is that of static vs dynamic typing. I've heard a million arguments from both sides throughout my entire career, but seen very few of them ever convinced anyone of anything.
Ruby with explicit, static typing would be like a salad with a scoop of ice cream.
-
One of the longest running schisms in programming is that of static vs dynamic typing. I've heard a million arguments from both sides throughout my entire career, but seen very few of them ever convinced anyone of anything.
Ruby with explicit, static typing would be like a salad with a scoop of ice cream.
I believe the argument is that everyone is realizing that dynamic typing sucks, which is why TypeScript is so popular and why "new" languages are static typed. Of course, maybe this is just the
WrongMarc
dynamic type. :laugh:Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity Framework -
One of the longest running schisms in programming is that of static vs dynamic typing. I've heard a million arguments from both sides throughout my entire career, but seen very few of them ever convinced anyone of anything.
Ruby with explicit, static typing would be like a salad with a scoop of ice cream.
The one that believes, doesn't need any proof. The one that doesn't believe, wants no proof.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.