Yes I do compile my kernel without Rust how could you tell?
Yes I do compile my kernel without Rust how could you tell?
Falling into your wing while paragliding is called 'gift wrapping' and turns you into a dirt torpedo pic.twitter.com/oQFKsVISkI
— Mental Videos (@MentalVids) March 15, 2023
>another contrarian thread
grow up
No
"oh no soneone compiled the kernel in a way I don't like"
lmao grow up
You are unemployed that's how I can tell
Still using 5.10 kernel with selinux missing. No rust code here.
Do you use gentoo?
GIWTWM
needs chicken sandwich correction
$ zcat /proc/config.gz | grep HAVE_RUST
CONFIG_HAVE_RUST=y
>Why yes, it is true that I don't have autism. How could you tell?
The only two acceptable ways: Disabling Rust because you care or not disabling Rust because you do not care. If you keep Rust enabled because you want it, get the fuck out.
trannies think that if they do free work that means we all have to stop using linux. on the contrary im here to take advantage of whatever free work they do, before their inevitable meltdown after they realize that they can't stop me from using their free software
rust in the kernel? sounds good to me, slong as i'm not the one writing it
>sounds good to me, slong as i'm not the one writing it
The issue is that Rust binaries are huge, unoptimized and take ages to compile compared to binaries from C code with gcc or clang. It took C compilers ages to not be shit. Same with Rust. I hope gcc solves that.
>Rust binaries are huge, unoptimized and take ages to compile
They are definitely larger than C and take longer to compile, but for the shit i've used it's never been so bad that i care that much. But unoptimized? LLVM seems to do a pretty good job. Even if it's not quite as good as a C compiler, rust programs are still better than node.js AIDS any day (and certainly faster than python programs any day.) and by this point i'm kinda dependent on ripgrep anyway so there's not really much i can do about it anymore....
>I hope gcc solves that.
logically seems like it could. in all honesty rust doesn't seem all that different, from a compiler perspective the biggest thing i can see is that the unit of compilation is entirely different
>rust programs are still better than node.js AIDS any day
well yeah, eating dirt is preferable to eating shit; I want neither.
for the end user of a rust program, it's just not that bad, just nothing like node.js.
Go is the real winner though. I don't even care that it's israelitegle's shit baby, Go programs are a great balance of easy to compile, decent performance etc. the binaries are fucking huge but i just use `go run` half the time since it's literally fine to just compile them on the fly...
Rust, Go, and JS are the dark triad of annoying to install software. they've all got huge packages for their bs package managers and build systems and junk. they're the few languages where I'll always seek out a binary release because its just way too much of a hassle to install anything written in them from source.
>Go
>annoying to install
How? Winget or apt, it installs the compiler fine. "go install example.com/[email protected]" just werkz. Are you literally upset about it using a gigabyte or two of disk?
>Are you literally upset about it using a gigabyte or two of disk?
for something I don't use and is just a dependency of other programs that I do use? yes.
You're compiling from source - of course it's going to eat up some harddrive space. You've got clones of every repository in the dependency tree, many with redundant source for other build targets or vendored blobs, and a cache of every build object. What's your situation that you can be upset about very typical space usages for compiling large software projects? Most C projects only get a pass because you're liable to already have the object files they need to link to available.
>You've got clones of every repository in the dependency tree, many with redundant source for other build targets or vendored blobs
Not if I already have those dependencies installed, no.
My issue is with needing Go installed and the golang being bloated. I don't keep it installed as it is overly large and I don't need it other than specifically for compiling these couple (relatively small) go programs I use. its package is around twice the size of Python's, its far too excessive for something that's supposed to be faster and better. It shits up my home directory with this stupid .go directory, and it fills it full of bulking object files and shit. Sure you can change that directory, but I don't want it creating it one way or the other, it shouldn't even exist in concept. It sucks, its overly complicated and I want no part in it.
I SEE THIS FUCKING FOX EVERYWHERE I GO. GET HER OUTTA HERE
she's never coming back, is she bros...
>he doesn't know
I'm sure you can just AI generate more now.
it's just not the same. it doesn't have the same soul
imagine the smell
where is she posting now please tell me I need more fox girls in my life
How did they manage to make a worse language than java or JavaScript bros?
I would rather compile my linux without gnu
I can't tell.
>They're slowly introducing a fast, memory-safe language into the Linux kernel? Splendid!
>Splendid!
memory safety is a spook