How will Any Forums cope when rust gets added to the linux kernel?

How will Any Forums cope when rust gets added to the linux kernel?

Attached: 1652896374823.jpg (800x484, 50.26K)

I'm moving to BSD.

I'm already an LGBTQ supporter *and* a FLOSS advocate, so I'll have nothing to cope with.

It won't.
Rustards will probably try to create modules but I'll never install them and they'll never get added to mainline, so whats it matter?

by using something else, and rewriting the kernel in fortran

>I'm already an LGBTQ supporter
haha nice one bro you almost had me there

I have nothing against Rust as a language, but I don't want it in the kernel. The kernel should just use ANSI C because it's the most widely supported programming language on all platforms, and there are more people who use it than Rust.

Rust is already in the kernel by way of in-tree driver modules. Linus has given the green light to polluting the kernel with it as well. It won't be long before the first Rust code is in the kernel, although it will take until the heat death of the universe for it to supplant even half of the C code in the kernel. The first kernel release that requires Rust toolchain will be the day I switch to BSD.

cd /usr/src/linux
printf "C: " && find . -name *.c | lc && printf "Rust: " && find . -name *.rs | lc
C: 30481
Rust: 0

Quick question: are you literally fucking retarded? Your local kernel headers != the entire fucking linux kernel tree.

I'll take it as a sign to give into dysphoria and start HRT.

hm. i've read you on another thread already. i think i might know you irl given the progressivism. are you a spic (mexa) by any chance?

>/usr/src/linux
>not /usr/include

>The kernel should just use ANSI C
All useful C code uses nonstandard extensions.

>kernel headers
>*.c
>*.rs

Seems you're retarded.

I'm not kidding, "bro."
I run Gentoo, shun big tech corpos, use an offline password manager and an encrypted filesystem, program in C, C++, and D, have written an extremely shitty and novicey and minimal working bootloader in pure x86 but the important part was it actually worked, I've successfully installed LFS before but bailed when I noticed getting through the Xorg section in BLFS was gonna take me who fucking knows how many goddamn days on end, I've written a functioning client/server framework in pure bash that uses signals and shm for IPC and yes that's just as much a crime against humanity as it sounds like and I have ALL the regrets sister, omg, literally ALL of them. And that's not even all the languages I'm very comfortable with and knowledgeable in, that's just all the ones I actually have any continuing occasion to use.
I am more based and redpilled about privacy than about 70% of Any Forums, hate big data and love freedom and libre software more than also about 70% of Any Forums, know more about linux than about 80% of Any Forums, know more about kooding than about 85-90% of Any Forums, and I am an anarcho-socialist leftist liberal who hates racists, misogynists, homophobes, transphobes, and the obscenely rich, and I drink pumpkin spice lattes (while secretly hating on starbucks because they are a corporation), and you know what, I've been thinking about getting my hair dyed lately.
Cope.
Cry about it you little bitch.

Attached: sbeeb.png (1415x1485, 670.15K)

This is the technical ability of the average rust user.

Nope. I strongly doubt you know me irl, I know barely anyone irl, and I certainly don't talk about this shit to them.

thanks for the pasta bob!

Can I get a quick rundown for a total pleb?

No prob trips mcgee

Attached: monstrosity.png (1300x866, 1.33M)

/usr/src/linux is where the linux kernel sourcecode lives
printf "C: " just prints "C: "
find . -name *.c will find any file that ends with ".c" in the current directory (.)
lc is an alias to wc -l, which counts the number of lines (in this case the number of C files found)

>find . -name *.c will find any file that ends with ".c" in the current directory (.)
Not him but the correct way to do this is find . -name '*.c'. You have to quote the glob, otherwise your shell will interpret it first

This is true on ZSH but not on BASH. It's good practice to quote it for scripting, h

>This is true on ZSH but not on BASH
You sure it's not the other way around? I've run into this problem on bash before, that's how I knew.

Only with GCC-RS completed.

Attached: file.png (1167x609, 72.04K)

Thanks frens! :)

well then.
there was this obnoxious s j w on facebook with a brutalist website and you reminded me of him.
it seems like you're new here, so let me tell you that like 90% of the posts you read here are sarcasm. most people here are slightly left leaning too (including myself, except i am an L G B supporter for reasons which i do not wish to discuss in a technology board), and there is only one small loud minority of unironic /p o l/ tards.
so please, just join the banter or go back to r e d d i t (although you might have fun at /p o l/ if what you want is to feel heroic owning le heckin evil n a z i scum).

Your time is up. C will become extinct, just like the GNU in GNU/Linux. :^)

Attached: .png (1719x992, 62.3K)

>Linus has given the green light to polluting the kernel with it as well.
C is pollution. Rust is the solution.

>although it will take until the heat death of the universe for it to supplant even half of the C code in the kernel.
C is the least productive language in the universe so "until the heat death of the universe" in C is probably a few months in Rust.

>/usr/src
>headers
Rustards are pseuds and midwits?

>I did this and that
Irrelevant, you're a fag.