Details
Joined devRant on 10/1/2020
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
The other thing Rust fanboys don't seem to understand is that MOST programming languages are memory safe.
C/C++ lets you do things you cannot do with Rust and Swift. It assumes you are adult enough to understand what you're doing. If you want safe memory, then don't use C/C++. If you want the type of functionality and memory-access that C/C++ grants - then you have to accept it's open to memory leaks.
Rust also has its own problems, too, things like "moved variables can be a pain". -
Rust claims that it doesn't need a GC but one can question how does Rust handle linked pointer structures like trees and linked lists? Reference Counting?
January's Stack Overflow's 2019 survey revealed that despite developers' positive feelings toward Rust, 97% of them hadn't actually used it.
"There are only two kinds of languages: the ones people complain about and the ones nobody uses." -- Bjarne Stroustrup, creator of C++.
Funny thing is that most software developers also say they love sex, even though 97% of them are still virgins.
Rust just reintroduces all the shit that people who choose Java were trying to get away from.
Every time I see Rust talked about, the only thing that gets mentioned is memory safety. C++ is unsafe, Rust is safe, so use Rust. It is borderline hyperbole with many of the people who parrot it the loudest obviously not having significant experience in these "unsafe" languages. -
Yeah, they will stop getting crappy pointer bugs but the team with the talent level that wrote crappy pointer bugs in the first place will naturally and effortlessly find new types of bugs to create.
Companies like Microsoft claiming that they use C++ but all their base APIs are C (ie "Win32"). They all use structs with no constructor, they all have an uninitialzed "size" field inside that struct to indicate how big they are as a sort of versioning system, etc., etc. It's C, not C++. -
Take the Python 2/3 horror story for example - that surely pushed away many from ever adapting it even if it's appropriate for the situation.
Change languages then magically all the bugs stop happening is utterly impossible.
According to my intelligence, Mozilla is dumping large amounts of money to convince people that all this effort to reinvent the wheel will pay off in the end. -
You get what you sow. If you assume the programmer is an idiot, you'll end up with idiots programming.
That's the part that scares me. Apart that i wish Rust all luck but i'd rather use a language that's been stabilized over the last ~50 year than something new and shiny that is very likely to change and within years been incompatible with code i write today. -
Rust tries to fix issues at the wrong level. It tries to protect the programmer against them self. Some people like that. Some people hate it. But to mind pops what C# was trying to do: allow 'unmanaged' code to run if you could jump a few hoops, turning something that was clear and obvious in a language like C into an unreadable pile of messy C#.
Maybe Rust has to fight the reputation languages like C# have. But why not let the programmer fuck up, learn from the mistakes and after have an even better understanding what's happening, so you end up with an even better programmer. -
That's why C and to a lesser extend C++ is so popular: one can figure out pretty much which CPU instructions will be used in what other and to what instruction they are related to.
That's also why debuggers have little problem mapping instructions to lines of source code, because there's a 1:1 relationship. Something that's very desirable (a proper working debugger) when developing. -
As many of you know, Programming languages always have had parallels to religions. The less one knows the more one believes and the more believers a religion has got the more superior it is viewed.
The media attention Rust gets, while behind way behind Ruby, Go and PHP and even Perl, reminds me of Scienetology.
If it's not clear to the programmer what Rust is doing (and what it isn't doing), then it's not suitable as systems language. -
and only his Korean friend who is programmer could code.
The Redditor further claimed that his Korean friend tried teach him Python but he could not understand any.
Then he went on and told that while googling, he found a new language called Rust.
He started to use Rust and were able to program for first time because Rust is easy as Python.
Now, If any idiot with double IQ digit read this, you can see that this is clearly a big lie.