Why not just use Go?
Because you are have an existing app in Python. Because you need some library that is not available in Go. Because you prefer Python. All are valid reasons.
then why not just use threads/processes in python?
Show HN: Runloom – Go-style coroutines for Python free-threaded
11–20 of 36 posts
Re: Show HN: Runloom – Go-style coroutines for Python free-threaded
#12Earlier quoted context omitted.
Because you are have an existing app in Python. Because you need some library that is not available in Go. Because you prefer Python. All are valid reasons.
then why not just use threads/processes in python?
Because they are not the same as Go-style green threads/coroutines?
Re: Show HN: Runloom – Go-style coroutines for Python free-threaded
#13This is a seriously impressive project. I see your pitch is M:N work-stealing across real cores on free-threaded 3.13t/3.14t which i think is only possible because nogil now exists. which makes gevent seem lackluster in comparison
Re: Show HN: Runloom – Go-style coroutines for Python free-threaded
#14Earlier quoted context omitted.
then why not just use threads/processes in python?
Because they are not the same as Go-style green threads/coroutines?
Clearly lol. I think a good-faith interpretation of the question is: "What kinds of things is go's concurrency model suited for where the normal pythonic alternative is cumbersome/less desirable"
Re: Show HN: Runloom – Go-style coroutines for Python free-threaded
#15This is an intimidating amount of code! 12,303 lines of C and 244,740 lines of Python, which looks to be a ton of monkeypatching plus huge amounts of test code. Only one commit added all of that, just two hours ago. The published numbers are impressive, but its hard to evaluate how much trust can be put in a project of this complexity at this early stage.
250k lines of code in one commit is reason enough to disregard the project entirely, IMO. Vibe code if one wants, but that is just madness...
It's pretty obvious that the author didn't write a single commit during development, they just squashed their commits into a single commit at the end.
Re: Show HN: Runloom – Go-style coroutines for Python free-threaded
#16Earlier quoted context omitted.
250k lines of code in one commit is reason enough to disregard the project entirely, IMO. Vibe code if one wants, but that is just madness...
It's pretty obvious that the author didn't write a single commit during development, they just squashed their commits into a single commit at the end.
Whether they did that or had an LLM one shot it, I dont really care. Commit history is pretty important if you ever want to try fixing bugs or improving features in the future.
Re: Show HN: Runloom – Go-style coroutines for Python free-threaded
#17This is an intimidating amount of code! 12,303 lines of C and 244,740 lines of Python, which looks to be a ton of monkeypatching plus huge amounts of test code. Only one commit added all of that, just two hours ago. The published numbers are impressive, but its hard to evaluate how much trust can be put in a project of this complexity at this early stage.
Code is a liability, not an asset.
Re: Show HN: Runloom – Go-style coroutines for Python free-threaded
#18Earlier quoted context omitted.
It's pretty obvious that the author didn't write a single commit during development, they just squashed their commits into a single commit at the end.
Whether they did that or had an LLM one shot it, I dont really care. Commit history is pretty important if you ever want to try fixing bugs or improving features in the future.
[deleted]
Re: Show HN: Runloom – Go-style coroutines for Python free-threaded
#19This is an intimidating amount of code! 12,303 lines of C and 244,740 lines of Python, which looks to be a ton of monkeypatching plus huge amounts of test code. Only one commit added all of that, just two hours ago. The published numbers are impressive, but its hard to evaluate how much trust can be put in a project of this complexity at this early stage.
I just copy pasted the work from my old repo into the main one. The main reason was hundreds of MD files and agent results were added into the repo that would have been impossible to clear from history.
This wasn't all written in one shot. I built the project over several months and spent the whole time testing it. Most of the code in the repo is QA / tests.
I had written an article that speaks about the project that I'd hoped would get upvoted (instead of this github link.) It speaks a lot about where the project aims, how it works, and the testing process, (read about my testing process at the end):
https://robertsdotpm.github.io/software_engineering/goroutin...
Re: Show HN: Runloom – Go-style coroutines for Python free-threaded
#20How does this compare with gevent?
Gevent runs in a single thread. Runloom lets you use every single thread at once and run millions of fibers.