11–20 of 53 posts
This doesn't say a lot about the current state of Python. It's just a list of the libraries that the author happens to know. Presented not in list form.
A couple notable omissions: Guido now works at Microsoft. pybind11 is probably the latest and greatest for C++ interop.
No love for Tkinter?
Although subjectively the look on Windows 10 seems a bit better than on previous versions, it still feels a bit ancient. So you may ask what's the point: if you create a GUI in 2021 you will probably want it to look modern and attractive. Even a modern TUI interface may look better.
Python's goal that "there should be one obvious way to do anything" is admirable, but doesn't seem like it's lived up to in any way.
Say what you will about Golang, but I do like the fact that it won't even compile if you don't follow the mandated codestyle. I don't want to have to think about stuff like that when I have actual problems to think about.
Every now and then I consider revisiting Python (I haven't used it in anger for a few years), but I am continually put off by the wild-west state of dependency management, lack of standard tooling and project configuration. Python's goal that "there should be one obvious way to do anything" is admirable, but doesn't seem like it's lived up to in any way. Say what you will about Golang, but I do like the fact that it…
I don't think that was ever a serious goal, it's just that initially Python competed with Perl, and Perl's slogan was "There's More Than One Way To Do It". Python didn't have as many different ways of doing the same thing in the language itself, and Python people liked that, so its slogan became the opposite.
Since Python 2 and 3 there are already far more different ways to do things in the language (like several ways of string formatting, etc) so it's more of a historical thing. And it was never the case for tooling.
https://www.jetbrains.com/lp/devecosystem-2021/python/
https://www.jetbrains.com/lp/python-developers-survey-2020/ (in partnership with PSF)
In my office, everyone seems to avoid python like fire. The big reason seems to be that lack of static type checking makes their work harder in the long run.
In my office, everyone seems to avoid python like fire. The big reason seems to be that lack of static type checking makes their work harder in the long run.
Do they avoid all dynamic typed languages or only Python in particular?
Every now and then I consider revisiting Python (I haven't used it in anger for a few years), but I am continually put off by the wild-west state of dependency management, lack of standard tooling and project configuration. Python's goal that "there should be one obvious way to do anything" is admirable, but doesn't seem like it's lived up to in any way. Say what you will about Golang, but I do like the fact that it…
> Python's goal that "there should be one obvious way to do anything" is admirable, but doesn't seem like it's lived up to in any way. I don't think that was ever a serious goal, it's just that initially Python competed with Perl, and Perl's slogan was "There's More Than One Way To Do It". Python didn't have as many different ways of doing the same thing in the language itself, and Python people liked that, so its sl…