truthpill me on Rust
no memes
Truthpill me on Rust
Alexander Morales
Other urls found in this thread:
semver.org
doc.rust-lang.org
twitter.com
Carson Garcia
SJW infested garbage
A community that's full of retard shills
A syntax so ambiguous that one character can mean 4 fucking things, made only for jerking off to unreadable code.
Philosophy of impossible safety, defaulting to unsafe code inside the main library, but who cares, it's a selling point!
Watch as any Rust tranny is going to try to debunk this. They're too busy swallowing HRT pills than to actually write something productive.
Ayden Walker
fpbp perfect description
Henry Carter
Very fast procedural safety-oriented language with a hint of functional. Somewhat steep learning curve if you don't get the hang of the ownership/borrow/lifetime system which basically forces you to write good code. You can go full low level and make operating fucking kernels in it or throw that out the window and use high level concepts like polymorphism (although limited). Relatively new so you won't see it everywhere for a while, mainly crypto is picking it up but cloudflare and some other relevant names are picking it up too.
The main response you'll get in Jow Forums is something related to the sexual orientation of the developers, although that's not related to the language and ahahhaha as I'm typing this would you look at that! I'll gladly debunk you, cnile-user.
>sjws/trannies/people who i dont like
Does not affect the language! Not an argument, fuck off back to Jow Forums
>A syntax so ambiguous that one character can mean 4 things
You're thinking of C++, Rust often enforces more explicit code to avoid that very thing. If you think you're still right, feel free to post an example.
>Defaulting to unsafe
Yeah, and you completely missed the point. The point of unsafe{} is to clearly mark unsafe operations as such, and many things can't be completely safe (ex: even a linked list). There's no "defaulting", there's code that can be provably safe at compile time, and code that cannot.
Ethan Nelson
>operating fucking kernels
Nice. It's 5am, meant to type "operating systems/kernels"
Robert Moore
The language is not limited in what you can write in it, so don't be silly and think it is.
It's quite unambiguous, with an easy to follow syntax imho.
The borrow checker is quite a different concept but it makes sure you write good, memory safe, code. Which is great, because it means: no Garbage Collector, and no free()s anywhere.
People have already written all sorts of things in it, e.g. OSs, kernels, loads of programming languages, game engines (including many games), &c.
Angel Thompson
>Does not affect the language! Not an argument, fuck off back to Jow Forums
Imagine getting denied community help because you're banned for having a political opinion that's right of Stalin. I'm sorry but it's their position to bring in politics, I fight fire with fire.
>You're thinking of C++, Rust often enforces more explicit code to avoid that very thing. If you think you're still right, feel free to post an example.
'x', 'a, &'a - what fucking explicit code are you talking about? Rust's syntax is an absolute hell to read, if you still think that it's as clear as any other language, fucking see the async implementation, it was the tipping point when I lost ANY respect for Rust.
>There's no "defaulting",
Yes, however Rust uses unsafe() to an absolute hell, this misses the point where you said
>safety-oriented
David Nelson
fpbp
Alexander Nelson
>denied community help because politics
No, you get denied for going "lmao fuck trannies and niggers and faggots fjfkgjdjgjdsf I can't contain myself and have some human decency for the people around me"
>'x' 'a &'a
single quotes have always been used for characters in low level languages. the latter 2 are identical meaning, first being "lifetime" and second being "borrow with specific lifetime"
>what explicit code
explicit typecasting, something even c doesn't enforce, no ++ op and often required in expressions with many () where two meanings could be interpreted depending on how you read it
>it's absolute hell to read
C++ is still much, much uglier for me and I've only used Rust for 2 months (vs. 5yr~ ish of C++)
>It uses unsafe, "missing the point"
That's why only features that have been tested to every extreme on every target platform make it into the stable branch if they have unsafe code in them. You missed the point again, the point of unsafe is to mark it as such. If it's stable then that's fine.
Ryder Flores
(what I'm trying to say with the code ugliness thing is that it's subjective, if it's unclear in that post)