Rust (the language) hate thread

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Creative Username said:
jesus fuck you can't even effectively hate rust because you're just completely retarded
rust is a slightly more strict-by-default version of c++ that retards shill as the second coming of christ (it really just makes computing more complicated than it's worth though)

it doesn't involve a bytecode vm at all like java does, and it also doesn't traditionally have a garbage collector like java has, and it essentially has no relation to java at all except for language-level memory safety and being shilled by retards to no end
also java has been free software for a good while now (see openjdk, the reference implementation)
Click to expand...
Oh. All I know is that Hyphanet uses it now after switching from Java (which I2P currently uses still). I thought there was a relation.
 
StolenWindows said:
Oh. All I know is that Hyphanet uses it now after switching from Java (which I2P currently uses still). I thought there was a relation.
Click to expand...
no there's really no relation and it may be a sign that this project is going down the drain because trying to rewrite in the current trendy language of the week only gets anywhere 20% of the time
it's basically like if they were trying to rewrite it in c++ because when you read "rust" you need to see the words "overhyped dialect of c++"
 
Creative Username said:
also this thread is for hating the rust language, not the rust community
Click to expand...
Ahem:
cover2-3173334862.jpg

lizardwizard said:
Linus doesnt give that much of a fuck anymore. So he's willing to suicide the projects before he retires lmao
Click to expand...
I believe its the other way around, where he is attempting to secure a future for his legacy by inviting as many potential maintainers as possible.
What he doesn't realize of course is that he is attracting the worst kind of people so its all in vein.

People are so fed up with the Rust shills that counter-shilling is emerging:
ahkdsa.png
 
(Apologies for double posting, but I believe it is warranted.)

G6FNnF2XIAApjps.jpg

The cope is of course that it wasn't actually just that one line, it was a series of programming failures and it is not the language's fault.
At face value, this is true, however the problem is that Pust is supposed to be better.
> After all, it is the mostest safest language and it forces you to be correct all the time!!!!4!
Except, clearly not. This could have been any language, but only one is shilled with the promise that shit like this won't happen.
 
Private Tag Reporter said:
it's almost like panic-as-default is bad programming practice.
Click to expand...

And we've been through this before. There are multiple reasons why C won out over Pascal, but one of the two biggest ones was that in Pascal, memory can only be allocated by calling the standard procedure new, which immediately terminates the program with an error if it runs out of memory (whereas C's malloc and friends return a null pointer on out-of-memory conditions, which gives you a chance to free up memory used for things like caching and then try the allocation again).
 
Unimaginative Username said:
And we've been through this before. There are multiple reasons why C won out over Pascal, but one of the two biggest ones was that in Pascal, memory can only be allocated by calling the standard procedure new, which immediately terminates the program with an error if it runs out of memory (whereas C's malloc and friends return a null pointer on out-of-memory conditions, which gives you a chance to free up memory used for things like caching and then try the allocation again).
Click to expand...
What version of Pascal is this supposed to have been?
 
306h4Ge5eJUJ said:
What version of Pascal is this supposed to have been?
Click to expand...

Both standard Pascal (ISO 7185, §6.6.5.3) and standard Extended Pascal (ISO 10206, §6.7.5.3). Note that the definitions of new provide no mechanism for regaining control if the allocation fails. It's possible that certain compiler vendors like Borland may have added non-portable procedures for allocating memory, but portable programs cannot rely on their existence. It is rather strange that they never provided a variant procedure new(var success: boolean; var ptr: ^T; ...) that takes a reference to a (non-pointer) boolean before the pointer reference and records whether the allocation succeeded or failed. All of this stems from Pascal's origin as a teaching language, where student programs aren't expected to allocate memory for things that aren't absolutely necessary for program correctness but are nice to have for performance (e.g., caching and memoization of functions), which you might be able to free if you run out of memory.

As an aside: To me, the strangest thing about Pascal's memory allocation is that Brian Kernighan didn't include it in his famous list of gripes about the language, though he did mention the other truly awful feature, namely that the bounds of an array are part of its type, so if you have an array of 100 integers and another array of 500 integers, you couldn't write a single procedure that can sort both, you had to write two nearly-identical procedures, at least until the standard provided the "conformant arrays" feature to alleviate this. (Also note that array [0..99] of integer and array [1..100] of integer are also distinct types despite having the same length, so in pre-standard Pascal they would have also required separate procedures for each type.)
 
306h4Ge5eJUJ said:
What version of Pascal is this supposed to have been?
Click to expand...
iiuc that was one of the biggest problems: every single pascal implementation did several important things very differently
Private Tag Reporter said:
it's almost like panic-as-default is bad programming practice.

error-flag-chads keep winning
Click to expand...
one of the designs i like for handling runtime errors like failed memory allocations is a nonlocal exit to some programmer-defined "oh shit" zone
this is also known to the unenlightened as an "exception handler"
 
Trigger Me Timbers said:
Click to expand...
The Merchants Guild sends its regards.

Rust Troony said:
Rust is a jeet language.
Click to expand...
Can you expand on this? When I think of a Jeet-stack, I think of this:
  • Some ungodly Vue or React BS at the top
  • REST API, HTTP/2.0 if you're lucky you get working certificates
  • 1,000,000,000 CRUD APIs that are copy-pasted
  • Java + Spring Boot Backend
  • 1,000 Microservice code nightmare, sometimes containerized
  • Whatever observability platform the university of Jeetistan pushed in computer science 101.
  • aws / azure / oracle etc
When I think of a Rust dev, I think of a tranny who masturbates to the idea of rewriting the same application 1,000 times to make it 'better' or 'faster', without actually knowing if it will see the light of day.
 
Sperg_rancher said:
Can you expand on this?
Click to expand...
It was more so intelligence based rather than actual about indians. People flock to Rust because of muh memory safety not realizing its just going to dumb down and lower the barrier of entry of people writing software in big projects, causing the overall quality of the project to suffer.
 
You must log in or register to reply here.
Back
Top Bottom