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.
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.
@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.
🏳️🌈
@dannyboy what makes it so bad?
@louiscouture depends on who you ask. For me, the most annoying thing is the bolt-on OO features. They make syntax inconsistent. Do you call func(obj) or obj.func()? Things like __self__ and __init__ are ugly and clunky.
@dannyboy __init__ is really annoying that’s granted but what I hate is the lack of brackets to delimit a function. I totally get that your code should be readable, but gosh it is annoying when you press space accidentally on something, and when you find out you have to back on all the lines of your code to remove all the spaces because the text alignment is off by one space,
@dannyboy Cancer caused by 'pylint'.
@dannyboy what's wrong with python?)
@odesa __self__, bolt-on OO features (is it func(obj) or obj.meth()?), the traceback is backwards, do I use my package manager's library or pip?, to name a few.
[sips in janet lisp