| > However, for most people, using Rust for these purposes is absolutely not recommended. Who are these "most people"? Can you get more specific here? > Java/Kotlin paired with reactive streams makes these tasks super easy to read, once you get the hang of reactive streams. Also there are complexities in there, you just simply can't brush all the intricacies of network programming and multi-threading under the rug, but at least you are dealing only with the complexities that are necessary for your problem. The text goes pretty much into detail. I do not understand where Rusts streams are more complicated than the Java/Kotlin/Scala ones? Did you
ever write an application with reactive streams and got problems with the thread pool, people unknowingly blocking in combinators, etc..?
I'd dare to say that these things also add complexity that is not necessary to the kind of problems you defined as "99% of ..." > With Rust you are dealing with tons of additional complexity that doesn't matter to 99% of people & problems. Where did you get that number from? What are "tons of additional complexity"? > I just find it very alienating when people compare this to Python and do everyday tasks with it. Maybe you just have not yet recognized that you can do everyday tasks with it? |