4 ms·
You should be using rust... mm kay :\
by awesome_dude 8mo ago
You should be using rust... mm kay :\
- danudey 8mo agoDoing concurrency in Rust was more complex (though not overly so) than doing it in Golang was, but the fact that the compiler will outright not let me pass mutable refs to each thread does make me feel more comfortable about doing so at all. Meanwhile I copy-pasted a Python async TaskGroup example from the docs and still found that, despite using a TaskGroup which is specifically designed to await every task and only return once all are done, it returned the instant theloop was completed and tasks were created and then the program exited without having done any of the work. Concurrency woo~
- awesome_dude 8mo agoThe person I was replying to sounded exactly like the Rust zealots roving the internet trying to convince people to change.
- deleted 8mo ago[deleted]
- Groxx 8mo agoYeah, I'd really have liked to see something like [Trio](https://trio.readthedocs.io/en/stable/ https://trio.readthedocs.io/en/stable/) gain mid more attention in Python. Structured approaches can prevent a huge amount of those issues, and Python code is absolutely riddled with concurrency problems in my experience. Much more so in practice than other languages except maybe javascript (when including async ordering mistakes). It makes it a real nightmare to try to build anything actually reliable.
- anthk 8mo agoSo you are trying to explain concurrency to the folks who implemented CSP in both Plan9 and Go. Interesting. I should return "cspbook.pdf" back.
- awesome_dude 8mo agoOne day, maybe today, you will learn to read
- anthk 8mo ago(eval) rather than (read), then. On concurrency, Go has the bolts screwed in; it basically was 'lets reuse everything we can from Plan9 into a multiplatform language'.