My thoughts on Static vs Dynamic Typing (Python Edition)

@tsoding That's great! But ST doesn't actually work like that. It only checks if all APIs are compatible with each other. "Meta-execution" is more about model checking and theorem proving. ST, like DT, can have a lot of bugs related to user-generated and other side-effects

@tsoding That's completely true, but dynamic typing is very handy sometimes. I think it's more about choosing the right tool for the job.

@tsoding This is why I write tests c:

@tsoding They have optional static typing now. But the problem is that it's, well, optional :)

@tsoding It does not go through an “meta execute” your code in a static language. It checks your code syntactically and then makes sure everything links correctly (the symbols). Static compiled langue’s still have runtime errors and crashes

@tsoding I write a lot of Python and C# day-to-day. I always choose C# first. I think there is a time and place for Python, but the advantages in using C# in Visual Studio or Rider usually out weight the benefits of any dynamic language.

@tsoding There are many advantages to statically typed languages. The shift of JavaScript to TypeScript shines a light. STL add overhead but have ecosystems with better tooling that compensate for the cost the "boiler plate" needed. Most statically types languages have a dynamic runtime.

@tsoding Hm…. Try to discover how many bugs have you fixed which causing wrong ST or business logic. It’s really interesting exercise for brain. And in my opinion using ST everywhere is a wrong way the same as OOP 😼