Rust (the language) hate thread

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.

5000% Sure

Defendant is a fat black woman - Bowman v Mitchell
kiwifarms.net
Joined
Feb 5, 2022
1646116393232.png


Hate-post about Rust, especially its troon-filled community (I stg you could find like 30 cows just by looking into Rust community members). Posting about the more technical stuff (lang features etc) is also fine though.

I'll start:

Screenshot_20220520_170033.png

I've noticed a lot of these troons seem to legitimately think that "is run by soys and trannies" is a selling point and a serious reason to choose Rust, and they list it right next to the actual language features like it's some great technical achievement. Hilarious.


Someone paid Hank Green a bunch of money (I would guess like $50-100+, but can't find anything to back this up) to have him shill the language in a video:

lmao
Screenshot_20220528_055353.png



A year or so ago they used to say on their website that their mascot was a literal non-binary crab:
Screenshot_20220528_052316.png


In typical troon fashion, they changed this to make it more incloooosive:
Screenshot_20220528_052336.png



From their official Code of Conduct:
Screenshot_20220528_063023.png

Screenshot_20220528_063402.png
 
Last edited:
memory safety is a meme lol allocate your memory normally and it's your fault if you forgot to free a pointer and suddenly you have your program using 6 gb
generally i think that unless you're writing something super low level (like an os kernel or a device driver) you are better off staying away from manual memory management. just use c# or java or any of the million other languages that have garbage collection to take care of these things for you. there's really nothing wrong with using these. fat neckbeards might call you a n00b for not being a hardcore l33t h4x0r who writes assembly by hand and has his own homemade c compiler, but who cares lol
 
Gotta say, I've been very impressed with Rust so far.
I didn't think we could get a language to compile slower than C++ but they smashed that record and made it take up shitloads of ram too.
The package system where you can just squat on as many names as you want with no recourse is a great example of Rust's lucrative business potential.
Their 100% SELF HOSTED COMPILER which then passes off disgustingly bad bytecode to a huge binary blob of pure C++ is direct proof that Rust has uses in real world applications.
Their self-hosted backend "Cranelift" is going so well that it doesn't even have it's own repo anymore and has been completely absorbed into it's webassembly exclusive parent project.

memory safety is a meme lol allocate your memory normally and it's your fault if you forgot to free a pointer and suddenly you have your program using 6 gb
Join me in being very very surprised that millennials can't understand the concept of "You took out a loan. Now pay it back.".

What is the language itself like, though?
Imagine if javascript and pearl had a baby.
 
i have no idea about perl but i have had the misfortune of using javascript occasionally, and that has made me absolutely fucking despise the abomination that javascript calls a type system
Rust doesn't have some horrible prototype based type system. (It's knockoff OOP with interfaces instead) I was more talking about the abundance of giant javascript style method chains.
 
  • Like
Reactions: The Anarki Main
generally i think that unless you're writing something super low level (like an os kernel or a device driver) you are better off staying away from manual memory management. just use c# or java or any of the million other languages that have garbage collection to take care of these things for you.
Even C++ provides memory management primitives. But memory management isn't hard. If you allocate memory, free it when you're done with it. (In Linux, you don't even need to bother, as the OS plays janny after you exit, just don't allocate more memory than you have) It's literally that simple, but the midwits and lackwits trying to program can't even grasp that simple logic.

The reason Mozilla, etc. even developed Rust is because when you write a JavaScript interpreter, you run into all kinds of potential memory allocation errors because you're permitting the execution of arbitrary interpreted code. This is something that isn't anywhere near as easy to manage as your usual memory management case. Java evades this by preallocating everything it could potentially use when it first runs.

Null using Rust for SneedForo is a good idea if only to further harass the idiots who treat Rust like their own private political soapbox. It's a canny move.
 
What the fuck with this Code of Conduct, basically victim blaming and absolute lies that the trannies are right and will assume goodness from a person to be bullied.
Even C++ provides memory management primitives. But memory management isn't hard. If you allocate memory, free it when you're done with it. (In Linux, you don't even need to bother, as the OS plays janny after you exit, just don't allocate more memory than you have) It's literally that simple, but the midwits and lackwits trying to program can't even grasp that simple logic.
The basics of memory management is basically don't and just use some basic vector/map to do it for you. But if you must then just keep it simple so constructor allocates and destructor deallocates.
Ditto for pointer use.
 
Seems to me like a key part of endorsing Rust is making sure you spend at least 30 minutes talking shit about about every other language in existence first. Some Rust fanatic unironically said that even the simplest 50 lines of Python took him minutes to write, but "several hours" to "properly" debug. They claimed that the same code in Rust only needed to be written once, and didn't require debugging because it was impossible to write Rust improperly (?)

The strategy seems to be: 1) Make every language sound "unsafe" and that your C/Python/Whatever program could be doing any number of crazy things behind the scenes without you knowing, 2) Paint Rust as a language that should replace every other language on Earth due to aforementioned unspecified safety issues in other languages, 3) Include "Written in Rust" as a feature for any program written it, despite it not meaning anything to the large majority of people reading it.
 
Even C++ provides memory management primitives. But memory management isn't hard. If you allocate memory, free it when you're done with it. (In Linux, you don't even need to bother, as the OS plays janny after you exit, just don't allocate more memory than you have) It's literally that simple, but the midwits and lackwits trying to program can't even grasp that simple logic.
this and people choose lockless threading because locks are slow.

The fact that rust is 'safe' is only going to make the code within unsafe blocks that much more shit, because rustfags won't be used to coding without the safety assumptions.

Though I kinda want to learn it just to be able to follow what gamozolabs on youtube does. Fuuck that though, the syntax gives my eyes cancer.
 
Serious question from a mere server infrastructure monkey: Are there any programming languages that DON'T suck ass?
Snarky coder retort: First you have to define what you mean by "suck ass". As someone who started programming just shy of 30 years ago, there are a lot of incredibly powerful programming languages with some incredibly useful properties.

Here are the issues:
1. Humans are retarded.
2. Programming languages are designed by humans.

It all comes down to choosing the retardation that doesn't irritate you and helps you get your work done faster. I do not believe that humans are intelligent enough to be good coders. All the best pros I know have extensive catalogues of cope strategies used to deal with the fact that they suck at what they're doing, and these strategies help them suck less.

For example, my favorite language is Prolog. Good luck doing anything "normal" with it. No good UI toolkit (that I've bothered with) but it has a bunch of tooling for weird edge case usage that few other languages have, such as constraint logic, definite clause grammars, heavily customizable operators, and ridiculous metaprogramming facilities. I have this weird academic metaparser that extends EBNF syntax to parse arbitrary code based on a grammar spec that I've developed in a couple hundred lines of Prolog. "Normal" people often use some kind of LISP or Haskell (or even Ada?) for these purposes.

For "normal" usage, I like C and Ruby. I like C because whatever you want to hook it to, you can. Integrating with C is a feature that almost every software/development package touts to some degree. C sucks because you have to manage memory, and most non-trivial cases of dealing with string information involve managing that memory.

Ruby sucks even more than C. It's slow. It's obscure. But it doesn't irritate me like Python, which is what most "normal" people would use in this use case instead of Ruby. Unlike C, Ruby has some ridiculously expressive string handling. If I'm looking to do network stuff or string mangling, Ruby's what I go to. Also, if I'm looking to do something non-trivial in C, I'll do a prototype in Ruby first, because that helps me get my ideas in order, and it ends up saving development time. I'm about 5 times faster to produce a polished product in Ruby than C, though a big chunk of this disparity is that I'm a comparative noob at C.

The professional languages I've used are C# and Java. C# is better than Java, but both are used more-or-less exclusively in enterprise. If you're going to be developing in either, it's because you're employed by some corporation who has a contract with the provider. I'd pick C# all day over Java.

This is without getting into the domain-specific languages like bash, SQL, Makefile, etc. All these have great specific use cases where they shine, but there are really obvious cases where each of them couldn't be more useless and awkward.
 
Back