Programmer Humor

32483 readers

518 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 5 years ago

MODERATORS

[email protected]

676

STOP DOING ASYNC (lemmy.world)

submitted 9 months ago by [email protected] to c/[email protected]

63 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 7 points 9 months ago (41 children)

I honestly don't know, why async got so popular. It seems like the entire reason for doing it was that some blokes were hellbent on using JS on a server and couldn't fathom that a second thread might be a good idea.

[–] [email protected] 10 points 9 months ago* (last edited 9 months ago) (2 children)

Async rust with the Tokio Framework is pretty cool. Need none of that JS bloat for async.

[–] [email protected] 3 points 9 months ago (2 children)

Honestly I can't wrap my head how to effectively put computation into a thread, even with Tokio.

All I want is something like rayon where you got a task queue and you just yeet tasks into a free thread, and await when you actually need it

Might be too much JS/TS influence on me, or that I can't find a tutorial that would explain in a way that clicks for me

[–] [email protected] 3 points 9 months ago

Tokio specifically says not to use it for CPU intensive tasks and rayon would be better for this: https://tokio.rs/tokio/tutorial

Speeding up CPU-bound computations by running them in parallel on several threads. Tokio is designed for IO-bound applications where each individual task spends most of its time waiting for IO. If the only thing your application does is run computations in parallel, you should be using rayon. That said, it is still possible to "mix & match" if you need to do both. See this blog post for a practical example

[–] [email protected] 1 points 9 months ago

Tokio is for concurrency, not parallelism. Use it for IO stuff. They say rayon is good for that, but I haven't used that. If you just want something simple, I'd recommend working with threadpool.

[+] [email protected] -11 points 9 months ago (1 children)

Async Rust sucks. I hate how many libraries use it, forcing it apon you.

[–] [email protected] 7 points 9 months ago* (last edited 9 months ago) (1 children)

You suck, I hate how your comment was forced "apon" me. Anyone who claims things that they can easily avoid if theyre so opinionated against them are "forced upon" them are always pathetic people.

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago)

Have you programmed with rust a day in your life? Once you introduce one library that requires Tokio async you have to start wrapping all your calls that involve it in async shit.

So many better concurrency patterns out there.

And these libraries are not easily avoidable. Ex: most AWS libraries require it.

And forgive me for a stupid typo, I have had little sleep the last week but you are an asshole that thinks belittling people somehow makes you right so it doesn't really matter.

load more comments (38 replies)