Rust devs are, empirically, gay r-slurred s

It's hilarious how bug-ridden your short C code snippet is.

1. buffer contents aren't null-terminated properly, so printf will always do an out of bounds read. This is exactly the kind of bug that Rust is meant to prevent. BTW, even if it was terminated properly, it's generally a mistake to assume that an input file doesn't contain null bytes, you should instead use a function that takes the input size.

2. fseek and ftell are broken by design and they will not work with files larger than 2GB on the platforms where sizeof(long) == 4, e.g. Windows (both 32-bit and 64-bit) and 32-bit Linux.

3. The code doesn't check for ftell and fseek errors and potentially treats the error sentinel value (long)-1 as a filesize and passes it to calloc and fread.

Anyone who advocates for C/C++ as a good general purpose language is either a 150 IQ turboneurodivergent, or has never had to read code written by the former group.

You definitely don't need that fancy templating in the Rust version unless you're trying to be fancy or write a really nice API or something.

Just take a Path ref ffs

Why the frick are you writing in C and not C++. Disgusting code.

Imagine understanding any of this, if you want to read a file why not just USE YOUR EYES? Zoomers smh.

PHP chads keep on winning

echo file_get_contents(file);

Further detranified it for you. See all that whitespace to the right of your code? That's empty space waiting to be filled.

int main(void)
{
	/* declare a file pointer */
	FILE    *infile;
	char    *buffer;
	long    numbytes;
 
	infile = fopen("test.dat", "r");       // open an existing file for reading 
	if(infile == NULL)  return 1;          // quit if the file does not exist 
	fseek(infile, 0L, SEEK_END);     numbytes = ftell(infile);    // Get the number of bytes
	fseek(infile, 0L, SEEK_SET);	     //  reset the file position indicator to the beginning of the file
	buffer = (char*)calloc(numbytes, sizeof(char));        //  grab sufficient memory for the buffer to hold the text
	if(buffer == NULL)  return 1;        // memory error
	fread(buffer, sizeof(char), numbytes, infile);    // copy all the text into the buffer
	fclose(infile);
	printf("The file called test.dat contains this text\n\n%s", buffer);     // confirm we have read the file by outputing it to the console
	free(buffer);     // free the memory we used for the buffer
	return 0;
}

Cargo is also a package manager which is great. It's the C++ equivalent of conan and cmake merged into one, but it's coherent and not shit. Conan makes me want to commit terrible acts of violence, and it's still the best C++ package manager around - although maybe you could argue that most conan issues are really packaging issues because the people writing C++ packages for it are actual subhuman r-slurs.

Strags are officially an underrepresented community among Rustaceans

I don't have a single irrational belief

Don't you sometimes get that feeling, when you're trying to figure out some bug, and then realize that logically the code should have never worked at all, and you're like, whoopsie daisies, looks like I'm dreaming and I finally dreamed myself into a logical contradiction with no other escape than to wake up?

its fricking hilarious how jeets use a class-only language

The chart is a breakdown of the 15% who said they were part of a marginalized community.

Smartest wh*toid