janine9vn
commented
2 years ago This conversation came up today in #community-meta and the overall consensus was that this is a tag + article on pythondiscord.com we want!
A good point was brought up that we'd likely want to call this tag !speed rather than !slow.
Now for the good part with lots of potential discussion...
What will we include in the tag/article?
- Python being a dynamic and interpreted language and what that means in terms of speed
- Why do we use Python? (Development speed, cost of dev time vs run time, strong ecosystem, great community, etc...)
- Is Python slow or is your code slow? Let's talk time complexity, data structure choices, and profiling tools you can use to see where the slowdown might be
- It'll be slow no matter what. Discuss limitations like File IO, user IO, bandwidth, and other factors that transcend which language you choose
Tag vs Article
I think the tag should be a short list enumerating the points and then at the bottom linking to the article that goes into much more detail. The article can have each of the points listed as a section header and link to other relevant articles and helpful tools. I think it's important that it be used as a teaching tool, so we should provide folks with links to profiling tools, articles about time and space complexity, and good descriptions of the real world, unavoidable limitations.
Are there are specific resources we should link to? Any specific wording we should try to use?
Tag Name
!slow
What kind of content should the tag include?
Can you guys make a !slow command for general chat? When someone comes in asking why/if python is slow, we type !slow, and get a nice little explanation on why python isn't actually 'slow'....
I see many times a day, "i heard python is slow, is python slow??, etc"