>>107024566Retarded safety model.You can write invalid Haskell programs that typecheck, but you can't do the equivalent of that with Rust. In fact, there are many programs that should borrow check but don't.The compiler is more strict than Haskell's, and Haskell is widely considered worthless for real applications.Let that sink itMoreover the safety model is all or nothing, either your function fulfills all the safety requirements or it's "unsafe" and anything goes. A more flexible model with different degrees of unsafe would be better. Every once in a while you will read about how someone wrote a driver for this or that in Rust, but when you look at the code it's just full of unsafe blocks everywhere. And don't get me started in trying to write GPU code in Rust.Having different threads access the same memory location is not a big, it is a very useful and often necessary thing for programs. Those are perfectly legitimate usecases with algorithms that are often probably well-behaved. Yet Rust shits the bed in this domain. No one is going to waste compute making copies when the whole point of GPU programming is to get as much performance as possible, so the recommend course of action is to just wrap everything inside unsafe.All in all, Ada with Spark is a proven and reliable technology that, as of the most recent version, even includes syntactic sugar for the kinds of checks the Rust borrow checker implements. Use that instead, because this is a technology made by people who actually cared about applications, unlike Rust which was made by webshits and for webshits.
>>107024566Forced safety in wrong places and to the ridiculous degree which resulted in much slower development.
>>107024566>Pervasive (global) borrow checker instead of optional ownership enforced types>Retarded error handling>Bad semantic code (why is unwrap() like a function that can modify the program flow, why?; why is not it an operator?)>Hidden control flow>? how is that better than "try" or "propagate" or "fail" or "mayfail" and why postfix instead of prefix?>Retard and convoluted syntax>No capability types to enforce safe resource usage and authorization>Lifetimes annotations instead of regions>Very opinionated library
>>107024566>Why did Rust fail????
>>107024566>fail
>>107024566a community more focus on force shove it in the throat of every project that doesn't require it , instead of understanding the real engineering problems and market. Many of Rustoddlers doesn't even know that Arduino for example use C++ and a lot of hardware companies still uses C/C++ and has their security standards so they give a fuck about Rust.
>>107024566>The compiler is more strict than Haskell's, and Haskell is widely considered worthless for real applications>Ada with Spark is a proven and reliable
>>107024983Was meant for >>107024641Also>Having different threads access the same memory location is not a big, it is a very useful and often necessary thing for programs. Those are perfectly legitimate usecases with algorithms that are often probably well-behaved. Yet Rust shits the bed in this domain.Why do nocoders keep repeating this?
>>107024566writing code is complex no matter what.rust tries its best to abstract the complexity. But the complexity is still there, in those arbitrary rules made by troons.i
>>107025011Rust has never tried to abstract the complexity. Quite the opposite, it autistically aims for perfect zero cost abstractions, no matter the cognitive overhead. That's what makes it white men only language.
>>107024803>>Retarded error handlingImagine being too much of a brainlet for monadic error handling.>>Bad semantic code (why is unwrap() like a function that can modify the program flow, why?; why is not it an operator?)It's no different from libc's exit() in terms of program flow.>>? how is that better than "try" or "propagate" or "fail" or "mayfail"Because it doesn't require explicit try blocks.>why postfix instead of prefix?Because it makes it more readable when chaining operations instead of try(try(try(foo.bar().baz()).faz().laz())) vs foo.bar().baz()?.faz().laz()??>>Retard and convoluted syntaxSuggest an improvement to syntax without losing its expressiveness.>>No capability types to enforce safe resource usage and authorizationCan be implemented through a library.>>Lifetimes annotations instead of regionsMemory regions are very limited in usecases and can result in quick resource exhaustion if you cannot put clear boundaries on allocation's lifetimes.>>Very opinionated libraryThe opposite, rust has very minimal library and it's up to you to choose everything above the bare minimum.
>>107025035
>>107025336You're using it wrong
Trannyware politics
>>107025336dumb retard
>>107024983>Ada with Spark is a proven and reliableBased. And just plain Ada is a lot more enjoyable too.
>>107024566Turns out linked lists are more important than the whole memory safety bs
>>107024949>493 million downloadsevery project that does more than hello world requires 1 million dependencies, so that was just 439 people compiling their toy application in the same day
>>107024566Rust was the one where Alec Baldwin shot his cinematographer, right?
>>107025035>That's what makes it white men only language.Rust is currently being pushed by Leftoids. White men are the ultimate evil to these troons.
>>107027973Rust is being pushed by largest tech corporations. Just like C, C++, Linux, Ecmascript, Vulkan and many other large projects.
>>107024983you are the clown since that was clearly bait as it got every point and sub-point deliberately wrong. and actual clowns would accidentally get the odd point right or at least half-right.
>>107028559
>>107028607no but seriously, that comment was like scoring 0/100 in a (proper) multiple choice exam. it would be as challenging for an actual retard to do as scoring 100/100.
