Guys and girls, This problem has been solved in 1980 already. Why are we still struggling?

It’s called Communicational Sequential Routines. Like, why do we have to come to full circles and Rust after a decade still hasn’t solved the “Async”/Multithreading problem. It’s mind boggling to me, Im sorry, people are gonna hate me for me being frustrated, but I just can’t say that it’s irritating that Rust, a language that really has offered many great ideas, STILL hasn’t figured out how to properly do things like channels and sequential communication? A concept that has been invented since the 80’s? Or if that doesn’t fit at least see how it could fit Rust’s standards?

It’s HORRIBLE that Rust as a language and community STILL uses Tokio and Async-Std and we can’t even decide always which one of the two to use and while they also have some incompatibilities afaik, and this is just for ASYNC. Multithreading and Async? God bless your soul if you’re going to do that in Rust, because prepare for debugging for days and for many weird issues and caveats.

Go, a much MORE inferior in features language has done it. What makes it so difficult to inherent such or a similar approach? It’s a simple concept. Channels. In and out. And syntax and scheduler like Goroutines to make it easy to have async AND multithreading without the caveats Rust has nowadays if you were going to do such thing.

http://www.usingcsp.com/cspbook.pdf

Cozx we went to a full circle. Back to sveltekit now until we find a better solution. Back then Virtual DOM was a feature, now it’s more of a bug.

I went in, and saw exactly … what I expected to see.

I vertical scrolling bar much smaller than my own pointer.

Why, would you even suggest Rust for web development unless it’s necessary? It wasn’t made for that.

Use Go, or Node. Why Rust? When just to build a proto server and an http server at the same time you need to debug for hours first just to see that it still doesn’t work. And then you have to find out how to make the Diesel work. Another big giant to learn. And then find out how to make Elasticsearch, Cassandra, or any other thing to work with Rust. Like … it’s a whole disaster if you’re going to web develop with Rust. Do you know how much my time is worth for the company? Why would the company want to spend my time that it rents, on developing web tools on Rust when just to have async and “too many servers” you have to read blogposts like this one and develop for hours just to make something simple work -unless necessary- ? When I can have if not the same even better results in Golang? Both in time, and performance.

With blogposts like these it really feels more and more that Rust’s community found a solution, and once they have the hammer, everything is a nail to them. Rust is a tool. A fucking nice tool. But it wasn’t made for that.

Use the tool for the job, not the job for the tool.

I saw esoterics and heavily opiniated jargon such as .each!writeln; and immediately said … “fuck this”. I don’t wanna learn another shitty scripting language that thinks it’s cool because it created its own esoteric opiniated jargon. A language that isn’t even POSIX standard. Thank you.

OH! I had read that in the past and it was awesome! It really helped me to make a comprehensive good CLI and I got to make many CLIs after that in the company and basically got promoted for being clean and good programmer while I just followed these basic principles.

I love that site, thanks so much for bringing this up again.