Linked list https://boards.4channel.org/g/thread/81594266
https://boards.4channel.org/g/thread/81767882#p81780838

-------------------------------------------------------------
We all agree Rust syntax is horrible. Here's a list of the major problems and how to fix them, and then maybe people will actually use it someday.
1. No block expressions. No implicit returns. Use the fucking keyword.
2. Take the colon out of declaration syntax. remove the question mark operator. Give us a real ternary operator.
3. Take the "!" out of macros. They should look exactly like function calls.
4. Take the pipe bullshit out of closures. Use balanced delimiters.
5. Take out the "::" that sometimes appears when using templates. There is no reason for having this.
6. Fix all the keywords that were renamed for no reason: "match" = "switch," "let" = "auto," "()" = "void," and so on.
7. Replace the stupid "=>" operator with real case labels so IDEs can actually highlight them.
8. Make mutability the default. Use explicit const for immutable variables and references.
9. Put the type before the variable, not after.
10. Remove the pointless "fn" keyword. It's redundant.
11. Put template parameters before the associated declaration instead of mixing them in with a bunch of other stuff where it's impossible to read.
12. Change "self" back to "this" and make it implicit.
13. Struct fields should be defined with the same syntax as declaring variables.
14. Remove "impl Bar for Foo." You should be able to see all the interfaces a type inherits from at the declaration site.
15. Remove "impl Foo." Methods should be defined inside the struct body, or declared there and defined at the top level.
16. Make parentheses mandatory in if/while/for statements. Make braces optional.
17. Bring back the three-part for loop syntax. There are things that simply can't be expressed without it.
18. Make lifetimes completely invisible. They're implicit some of the time. Make them implicit all of the time, or just remove them. If the compiler can't make this work without a bunch of arcane symbols the programmer has to type, there is no point even having the feature.

-------------------------------------------------------------

Poettering reject https://boards.4channel.org/g/thread/81954356
https://boards.4channel.org/g/thread/83447022
https://boards.4channel.org/g/thread/84293340
https://boards.4channel.org/g/thread/85329915
https://boards.4chan.org/pol/thread/392381065
https://boards.4channel.org/g/thread/88256283

-------------------------------------------------------------
1. The language itself is not stabe (it's standard libs are basically in beta).
2. The language is not guaranteed memory safe (you can disable it). And C/C++ also has ways to make it memory safe, so why use another new and unstable language?
3. Apparently Rust uses some kind of binary cache for all compilations. Meaning you never really compile *everything* from source, but always use some existing bins. The NSA would love this.
4. The dev community consists of deranged gender activists
-------------------------------------------------------------


-------------------------------------------------------------
>use cargo to manage deps
>dep updates api breaking all api calls
>api dev stupid and doesnt know this
>dev using cargo stupid and doesnt know this
>break mission critical app for years
>not discovered until after leaving company
>"updated project dep system to modernized system" on his resume
>company puts out a security bulletin recommending to stop using "modernized" dep system
>still on his resume years later
>caused all normally encrypted ssl queries to be in plaintext with his malarkey
-------------------------------------------------------------


-------------------------------------------------------------
C++ has 133 CVEs
STL has 11 CVEs
Boost has 16 CVEs
Rust has 386 (~25% of the CVEs that the Chromium code base has)

https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=c%2B%2B
https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=STL
https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=boost
https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=Rust
https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=Chromium
-------------------------------------------------------------


-------------------------------------------------------------
The worst possible thing that could happen to the trannies is that the Rust language actually becomes successful. For a tranny views Rust as a community rather than a tool, and success will mean vast swaths of new members entering "their" community with a fresh outlook. If troons were normal people, they would be pleased to have "given birth" [never gonna happen] to their creation and would proudly pass torch to the next generation. After all it is said that: society thrives when old men plant trees whose shade they will never sit under. Yet trannies are not normal well adjusted individuals, they're narcissistic perpetual malcontents; they're going to seethe, cope badly, and die sooner-than late.

Success will mean they enjoy being "enriched" by a new group comprised of practical business centric professional programmers and enthusiastic young hackers full of energy to enact change. No one is going to care about the chatroom entrenched rusty old tranny whose only claim to fame was writing a crate for "fearlessly" calculating the absolute value of a number many years ago. In reality whatever good work they did for free will be employed by the new generation and the worthless contributions will simply be, to borrow a phrase, "rewritten in rust". The trannies are early stage founders without any stake in the game. They'll either see the inevitable coming and take the Samson option to implode the community from within, or to paraphrase Jefferson, will be someday wake-up homeless in the reddit their sisters conquered. In any case, they'll never see the promised land.

What does this mean for you? Well if you can employ Rust to your advantage, use it. It's got a greater than 41% chance of making it, so keep an eye on it incase the industry does actually adopt it. Those freaks of nature are detestable abominations, but view them as demons who have been bound to work for you. Better yet, just pretend you cannot see them. Thanks for attending my Ted Talk
-------------------------------------------------------------

https://boards.4channel.org/g/thread/88902171
https://github.com/CompVis/stable-diffusion/issues/283

-------------------------------------------------------------
Anonymous 09/30/22(Fri)12:17:37 No.88906384▶>>88907737 >>88907864
File: rust.jpg (29 KB, 540x360)
29 KB
>>88905896
As a lead dev who have worked with projects being infected by rust, I can explain. The real answer isn't at all what most people think.

Ok so what happens is that there is some project, maybe it's corporate maybe it's communal. Then rust troons arrive all gung ho and start proselytizing about how rust should be used, they'll offer to work for cheap because they love rust, rusts memory management will save money and trouble in the long run etc. It's an easy sales pitch to corporate and the naive.

So some rust guy gets hired to do a piece of the infrastructure. He works hard and for cheap and gets the rest of the team into it. Then at some point it becomes obvious that it's a real hassle to have rust interact with shit that don't follow it's own rigid and autistic protocols. Say, you have an old C library or something you need to interface with, that your codebase has used forever because it just works. Now your rust team has to deal with that and it's a hassle. So much so that at some point it becomes obvious that the right call is to either go back, or to rewrite that C library in rust so it conforms to the neovagine. Due to sunken cost fallacy that's probably what corporate is going to go for, even though at this point they start smelling the coffee and realize they've been somewhat had. A small community project is probably just going to crash at this point and you'll find countless of those, where they get rust and then just die in a year or so for inexplicable reasons. In this way the process just continues and the reason people don't realize is that rust only works properly for it's intended purpose when it's all rust. Hence the saying "rewrite it in rust."

So you see, rust isn't really a programming language. It's a self-replicating computer virus.

I'm sure the name is completely conscious by the big tech players who push it as well. Like, your car gets a spot of rust, what do you do? You either remove it or your car will be a rusted wreck
-------------------------------------------------------------

https://boards.4channel.org/g/thread/88941589
Memory management done correctly is also hard, but Rust people are allowed to cry about that?
The Rust community is a world of fanatics. Exactly like the happiest people on Earth are religious fanatics, the happiest programmers are fanatics of their language. When discussing Rust, they will endlessly describe how brilliant this language is, and how all problems are solved in it; they will say that it is ideal for both low and high levels; they will claim that their programs are the safest and most correct in the world. And indeed, they have a special thing about security - you can hearhow this language made them fearless. Now let's ask ourselves a question: is a fearless person capable of writing secure code? Rust fanatics rely on the compiler for everything, because they really don’t know how and don’t like to program, they want everything to be done for them either by the compiler or by pure magic. None of them understand how this language works, and it is impossible to understand

-------------------------------------------------------------
>The very nature of such variables or values in this case are RAM cells, and the work of the program is to change them.
>This language is full of lies: it tries to be low-level despite its incredibly high-level nature
-------------------------------------------------------------


-------------------------------------------------------------
Anonymous 10/06/22(Thu)03:39:18 No.89013105▶>>89013159 >>89013225 >>89013498 >>89018709
>>89012959
its a hackjob. And is not fully-function in the least.

Literally rendering 1 frame, and then turning the gpu off and on again, and rendering another rather than actually coherently handling all of the transient memory.

This is a hack of a fucking job and they are trying to ride the hype train of both this "accomplishment" and of rust evanglists to become a micro-celebrity of some sort.

This is a flash in the pan.

Doing GPU programming for an M1 mac running a welfare version of linux is a niche within a niche within a niche within a niche.

Apple will come out with the M2 or M3, and all of this work will have to be restructured and redone and you're at the mercy of these 2 or 3 people keeping the driver up to date because the fact of the matter is no one else cares enough to put their best weight on a version of linux that is at the mercy of the spare time of 2 or 3 people that will hack whatever they can to get fame.

Also they sound like fucking elmo
-------------------------------------------------------------

https://frenschan.org/g/res/1140.html

-------------------------------------------------------------
Have you attempted to bootstrap Rust from source code yet? It's an exercise in frustration. It can't compile itself on anything that isn't x86-64 and maybe ARM. No one is attempting to fix this. They expect you to pull down their binary. Even if you do you'll discover every platform other than ARM and x86-64 isn't supported. This is why Rust is dead in the water.

The GCC guys tried to implement the compiler on their own and were fought tooth and nail the entire way. The Rust community doesn't want anyone else building tools around this language. It makes a lot of sense if you look who's sitting on the Rust foundation board.

For all the talk of "safety" Rust can not exist without C doing the heavy lifting for it. Which explains why the Rust community attempts to subvert so many C applications. They've done it with Firefox and now they're doing it with the Linux kernel. How can a language be safe when it depends so heavily on an "unsafe" one?

I see Rust, Go, and similar projects as being for webdev types. To these people the system is just a black box. They are not smart enough to figure out how memory works. Hence why they can't use it without taking a shit on everything in RAM. They claim they don't use C because it's bad. In reality they don't use it because they can't into malloc() and manually managing data flow.

It's hilarious watching these people rant about safety in Rust but then turn around and advocate for javascript on the server or browser engines for cross-platform "native" applications. You're right C, C++, and python are all you really need. When I was learning most would have said perl instead of python but times change.

I've personally found Rust very annoying any time it has been added to an application I use. Mainly firefox which I've used since the firebird days. I've tried various Rust applications that claimed to be better than their C counter parts. Most were not very good. They all suffer from being a PITA to compile from source code and not working across all the platforms I use. I don't see much of a future for the Rust language and I expect to lose popularity like all the other fad languages I've seen come along (Ruby and Rust are very similar community wise btw).
-------------------------------------------------------------

I very strongly think Rust is trying to play Trojan horse with FOSS projects. Either jamming particular licenses down your throat or using some kind of sponsored/ad enabled monitoring. I like Dart and flutter a lot personally, but that's clearly what Google wants.

-------------------------------------------------------------
Rust is basically C++ with a different standards board/body comprised entirely of big tech shills from Facebook, Microsoft, Mozilla, Amazon, and the other usual suspects. It claims to have a safe memory model but as has been described in this thread it really doesn't. Instead of managing dependencies manually it relies heavily on an npm-like database called crates. Where you pull down random packages from all over the place at compile time instead of having them on your local machine and simply syncing with git.

Its native compiler is written in C++ (LLVM) with an extension in its native language (Rust). It's a constant moving target unlike C++ where there are standard editions you can code against with a standard body that sets them every few years. Instead of getting your choice of multiple compilers you're stuck with the one that hasn't been deemed stable yet and probably never will be. You also lose support for most platforms when compared to C++. If you plan on doing anything outside of AMD64 and modern ARM you're shit out of luck. Even older x86 machines are not supported at all. They claim support for more architectures but it's a mostly a lie that relies on cross-compiling from an AMD64 arch machine.

Basically, the trannys made up an entire language because they were too stupid to avoid buffer overruns in their code. It has become mostly a power grab as they attempt to weasel an unfinished language into things like browser engines and even the Linux kernel. Just look at who sits on the Rust Foundation: https://foundation.rust-lang.org/about/

It's all trannys, women, and big tech shills.

I do not consider it worth my time to learn. Although I did write some shit in Rust just because I wanted to judge it fairly. IME the language and community are shit. A newbie would be better served learning C and C++ if they felt they needed more. I consider scripting languages like Python more powerful at this point than Rust. Since Rust is so slow at compile time and not supported by so many platforms. I also do not need the "safety" features it claims to have. Which I assure you will be broken wide open like everything before it given time. I do not put much faith in the Rust community to do anything correctly or admit their mistakes when they do happen.

Golang is probably a better bet if you want to learn a modern poz-langauge for system's programming. Although that is controlled by google as well so you're taking your chances with what happens in the future.

C is still king. C++ is cancer of course but Rust is another step beyond even it. At least with C++ you can ignore a lot of things and cherry pick what you want from it. With Rust it's all or nothing and you'll be spending a lot of time writing "unsafe" blocks anyway once you get beyond a toy project like hello world. Might as well just learn/use C and enjoy the benefits that come with it like portability and speed
-------------------------------------------------------------


-------------------------------------------------------------
Anonymous 10/09/22(Sun)05:42:49 No.89080404▶>>89080540 >>89080588 >>89080648 >>89080652 >>89080724 >>89080743 >>89080748 >>89080954 >>89081142 >>89081162 >>89081192 >>89084210
File: can't say nigger in rust.png (271 KB, 1104x3568)
271 KB
>>89079753
>>89079664
>>89079702
>>89079816
>>89079735
https://docs.rs/censor/latest/censor/static.STANDARD_WORDS.html
Holy fucking shit it's real.
This is absolutely a functionality that should be on the top of your priority list when creating a programming language, huh
-------------------------------------------------------------

https://boards.4channel.org/g/thread/89115140
[nmap] https://boards.4channel.org/g/thread/89683908

-------------------------------------------------------------
Anonymous 06/02/23(Fri)14:08:44 No.93819878▶>>93820139 >>93824502 >>93824945 >>93836282
Why is a Rust conference being managed by the Rust project itself? This kind of behavior is typical for pop culture like blizzcon, not something that is supposed to take itself seriously.
For comparison, cppcon isn't managed by ISO or even GCC.
Why is an apology for a Rust conference being posted on the "dev blog"? What does this have to do with Rust development?
Why is Rust the only language that has this sort of 'drama'? Not to say other language don't have drama, but usually this drama comes in the form of some controversial spec change, something that is technical and not emotional.
-------------------------------------------------------------


-------------------------------------------------------------
Anonymous 06/02/23(Fri)16:50:55 No.93821539▶>>93821914 >>93828441 >>93829241
>>93820419
Look at his twitter bio lol.
>The C Standard Cannot Be Replaced And Will Never Be Destroyed.
No wonder Rustaceans hate him
-------------------------------------------------------------


-------------------------------------------------------------
Windows 11 06/02/23(Fri)17:48:30 No.93822057▶>>93822291 >>93830268
File: file.png (445 KB, 592x1373)
445 KB
>>93819817
>people tried to tell them but got dismissed
yes, dismissed like they were just 'haters' or some other nonsense instead of listening and thinking.

>>93821488
100% facts
-------------------------------------------------------------


-------------------------------------------------------------
jokes aside, there are many other industry proven ways of having memory safe code
>SPARK
>D or other GC-collected langs
>LH, F* for formal verification
-------------------------------------------------------------


-------------------------------------------------------------
https://twitter.com/rust_foundation/status/1644132378858729474
Anonymous 06/03/23(Sat)15:40:24 No.93839631▶>>93839913
>>93830756
yeah, that was a wakeup call to those that thought only good things could come out of a language controlled by a bunch of globohomo corporations sitting on the "rust board of directors"
-------------------------------------------------------------

https://boards.4channel.org/g/thread/93819321

-------------------------------------------------------------
Rust is unsafe Anonymous 07/16/23(Sun)01:58:00 No.94715455▶>>94715513 >>94715603 >>94715770 >>94717483
Why is this garbage memed so hard?
>muh memory safety
No one uses Rust securely in practice.
1) Your dependencies will inevitably force you to use nightly which means a "curl | sh" install of rustup. rustup itself will not validate GPG signatures so compromised CDN -> rooted machine
https://github.com/rust-lang/rustup/issues/2028 has been open fore years
2) cargo build executes arbitrary code during the build (!)
3) everything is broken in npm-style leftPad packages that nobody will ever audit
Like how the fuck are you supposed to use it without being always online and getting auto-updates to latest CVE's?
-------------------------------------------------------------

[Unsafe] https://boards.4channel.org/g/thread/94715455
[Crate] https://boards.4channel.org/g/thread/95030434

-------------------------------------------------------------
Anonymous 07/30/23(Sun)02:16:40 No.95031786▶>>95037007
File: Screenshot 2023-07-29 at (...).png (67 KB, 784x904)
67 KB
>>95030434 (OP)
>thou should not engage in wrong think!
>thou should not research negative effects of the vaccines!
-------------------------------------------------------------


-------------------------------------------------------------
Anonymous 07/30/23(Sun)09:29:15 No.95040001▶>>95040084
>>95039427
It's not even funny, drama in the Rust community works the same way as in tranny communities. They advertise their gender/language in a very vocal and obnoxious manner and exhibit a cult like behavior. They can't shut up about how Rust is the perfect language for everything and force projects to include rust code even when nothing really justifies this extreme need for it.
Many Rust devs are unironic trannies and act as trannies too. It's not just a meme
-------------------------------------------------------------


-------------------------------------------------------------
Anonymous 08/08/23(Tue)04:36:14 No.95218777▶>>95228716
What annoys me is that there is not a single piece of Rust software that doesn't mention Rust in the description.
>a graphical calculator written in Rust
>a Rust implementation of herpes
>a sack of potatoes rewritten in Rust
Every. Single. Time.
-------------------------------------------------------------

[Binary] https://boards.4channel.org/g/thread/95472198

-------------------------------------------------------------
Anonymous 08/19/23(Sat)22:03:17 No.95472909▶>>95472933
>>95472707
Wtf... he's really doing this over 5 fucking seconds? Someone please explain the mental illness that plagues Rust users, it's absolutely bizarre. I'm all for improving performance, but holy shit when you're compromising on very valid security concerns and it was over 5 seconds of compile time to begin with? What the fuck?
-------------------------------------------------------------

https://veresov.pro/rustmustdie/

-------------------------------------------------------------
Anonymous 08/21/23(Mon)16:36:25 No.95508979▶>>95509003 >>95510484 >>95514857 >>95529389 >>95531659 >>95535001
>>95508223 (OP)
most people that talk about rust and how great it is havent had any real experience with it. i was the same, it was so good for fizzbuzz!

then i used it at work for 8 months, me and 2 more guys.
refactoring? its a nightmare.
change lifetime of anything? nightmare
Arc<>, Rc<>, ReffCell<>, etc, etc all over the code base
npm syndrome, want to use some lib? welcome 1000 dependencies

we went back to c++
-------------------------------------------------------------


-------------------------------------------------------------
Anonymous 09/06/23(Wed)03:18:41 No.95823710▶>>95823812
>>95797497 (OP)
Frankly, not working with the kind of people who use Rust is reason enough to avoid the language. Most of them are absolute morons who think that following fads makes them a good programmer. For example, they keep replicating the JavaScript npm clusterfuck where a program of moderate size can pull in 500 transitive dependencies, and they justify this obviously stupid thing by appealing to the "unix philosophy". Absolutely braindead.
-------------------------------------------------------------


-------------------------------------------------------------
Anonymous 09/11/23(Mon)08:35:57 No.95925526▶
>>95925364
>people noticed
they didn't! he then said he also did this without announcing two weeks prior and noone noticed it. they only noticed it this time because he announced it.
-------------------------------------------------------------


-------------------------------------------------------------
Anonymous 09/30/23(Sat)20:40:39 No.96315663▶
File: f8gCF1I.png (143 KB, 869x315)
143 KB
>>96290375
>immediately think of C
>even their insult is centered around C
>C lives in their head rent-free
the absolute state of rustroon
-------------------------------------------------------------


-------------------------------------------------------------
Anonymous 09/29/23(Fri)17:06:35 No.96290958▶>>96291013 >>96293615 >>96294640 >>96298373
File: image.png (208 KB, 1080x1090)
208 KB
>>96286125
>>96289195
>>96289239
>>96290375
a non retarded programmer could prevent this
rust is not immune to corruption and memory leaks.
there are many critical vulnerabilities in rust programs and modules, less than C only because this is relatively new language and barely being used, but this is not even close to be safe.
-------------------------------------------------------------


-------------------------------------------------------------
Anonymous 09/29/23(Fri)17:25:37 No.96291195▶
File: 1669877876487290.png (19 KB, 904x564)
19 KB
>>96291013
and introduces many other bugs while doing that

-------------------------------------------------------------


-------------------------------------------------------------
nonymous 09/29/23(Fri)19:06:42 No.96292620▶>>96292656
>>96292588
>what is canary?
>what is stack protector?
kys tranny
-------------------------------------------------------------


-------------------------------------------------------------
Anonymous 09/29/23(Fri)23:13:39 No.96296747▶>>96300026
>>96293615
>>The Rust Programming Language Standard Library
Is pretty much the whole language. There is no spec, only a reference compiler
There is no standard except for what comes with rustc

-------------------------------------------------------------


-------------------------------------------------------------
Anonymous 12/15/23(Fri)21:51:45 No.97908410▶>>97910432 >>97910528
File: file.png (1.57 MB, 1769x1674)
1.57 MB
>>97905178 (OP)
> be /g/
> hear constantly from rust trannies about ((((safe)))) it is
> anons take apart the libraries
> they're a fucking nightmare full of unsafe declarations just to get this shit to work
> rust shills and trannies decided to go silent over the safety claims
> rarely mentioned anymore
> OP discovers how bad it truly is
my condolences, op. you were warned.
-------------------------------------------------------------

https://blog.rust-lang.org/2022/05/10/malicious-crate-rustdecimal.html
[Memory leak] https://boards.4chan.org/g/thread/98310132
https://kiwifarms.st/threads/rust-the-language-hate-thread.120053/
