(评论)
(comments)

原始链接: https://news.ycombinator.com/item?id=43918237

Hacker News 最新 | 过去 | 评论 | 提问 | 展示 | 招聘 | 提交 登录 Asyncio 深入浅出:逐个 yield 重建它 (indooroutdoor.io) 15 分,来自 thunderbong,1 天前 | 隐藏 | 过去 | 收藏 | 1 评论 OutOfHere 22 小时前 [–] 并非想贬低这篇文章的解释,我很抱歉,但 Python 的 asyncio 与 Python 更新的无 GIL 线程相比,实在是逊色得多。前者隐式地不并行化,而后者则可以。这与 Rust 的 asyncio(例如 Tokio)形成了鲜明对比,我相信后者是可以并行化的。这种损失非常显著,我认为现在使用 asyncio 完全没有意义了。 回复 考虑申请 YC 2025 年夏季批次!申请截止日期为 5 月 13 日 指南 | 常见问题 | 列表 | API | 安全 | 法律 | 申请 YC | 联系我们 搜索:

相关文章

原文
Hacker News new | past | comments | ask | show | jobs | submit login
Asyncio Demystified: Rebuilding It from Scratch One Yield at a Time (indooroutdoor.io)
15 points by thunderbong 1 day ago | hide | past | favorite | 1 comment










Not to take away from the article's explanation, and I am sorry, but Python's asyncio is a pathetically inferior choice to newer Python's no-GIL threading. The former implicitly does not parallelize, whereas the latter does. This is in stark contrast to Rust's asyncio, like with Tokio, which I believe does parallelize. This is a sufficiently significant loss that I think it's silly to use asyncio at all anymore.






Consider applying for YC's Summer 2025 batch! Applications are open till May 13


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact



Search:
联系我们 contact @ memedata.com