Learning Go was a fascinating experience for me. While the language drives me crazy in dozens of ways, pretty much every weird idiosyncrasy was introduced to solve a very real practical problem. And it completely uprooted the way I think about concurrency and parallelism.
On the other, Rust's demands of concurrency and asynchrony, along with its comprehensive memory model, puts demands on my knowledge for which I lack the prior skills. So every textbook is a combination of lots of "Yeah I know that" yawns combined with regular "What the fucks!?"
Back when rust was still under heavy construction, "they" sold it to me as the concurrency of Erlang with the type safety of an ML and the speed of C++. While you *can* use FP paradigms in almost every language now that isn't how most programmers approach task decomposition (alas)
Serverless servers: Efficient serverless Node.js with in-function concurrency | Vercel News
Building a compute layer that is highly-optimized for interactive workloads, server-rendering, and APIs
In-function concurrency now in public beta | Vercel News
The best way to deploy your Next.js site.
"The key point of Elixir is concurrency and the concurrency model." Joe Armstrong youtube.com/watch?v=7BUO...
Add name Add v2 name Fix action name Fix artifact name Swap actions order Fix concurrency Fix concurrency 2 Fix concurrency 3 test test test tset aaaa a aaa
Once you master channels & wait groups, concurrency is fast, easy, and cheap.