I am seeing more and more people on various social platforms finally realize what a cancer Python is.
Me, a glorious embedded C programmer, who knew all along.
@dannyboy I genuinely think that dynamic typing is a *really* bad idea.
Even if you just look at it from a human perspective, not having a type checker leaves you open to so many issue where your compiler would just tell you "this makes no fucking sense". But instead you get some mysterious runtime error far away from where your mistake actually was.
Even if you just look at it from a human perspective, not having a type checker leaves you open to so many issue where your compiler would just tell you "this makes no fucking sense". But instead you get some mysterious runtime error far away from where your mistake actually was.
Follow
@servant_of_the_anime_avatars
I actually don't have very many strong feelings on this and I've lived on both sides. I love Ruby and the type conversation is pretty good. The interpreter would spit out a sensible error message about a 'to_s()' method being unavailable or similar. Because python is functional with tacked-on OOP, the errors are hard to track.
