39 ms·
> and then you'll have to deal with all of its weirdness: significant whitespace By "weirdness" here you apparently mean not having to worry about matching up
by zahlman 2mo ago
> and then you'll have to deal with all of its weirdness: significant whitespace
By "weirdness" here you apparently mean not having to worry about matching up curly braces, and getting what you want automatically just for indenting your code the way you're supposed to indent it anyway... ?
> truthiness
Which is different from how it works in other similar languages, how exactly?
> duck typing
Which is weird, how exactly?
> GIL
You can go a lot further than five minutes in Python without having to worry about threads at all, and if you do attempt threading, unless you're writing C extensions, the worst thing the GIL does is deny you the multi-core processing you thought you were going to get.
> distribution/packaging
Tons better now, but it was honestly never difficult, people just didn't care.
- ModernMech 2mo ago> Which is different from how it works in other similar languages, how exactly? They are contrasting with languages where true is true and 1 is 1; but true is not 1, and 1 is not true. > Which is weird, how exactly? Sometimes if it looks like a duck and quacks like a duck it can still not be a duck. > You can go a lot further than five minutes in Python without having to worry about threads at all Unless you specifically want to do multithreading. > the worst thing the GIL does is deny you the multi-core processing you thought you were going to get. That is the worst thing because I wanted that multi-core processing, that's the whole reason I wanted to do multithreading.