• 2 Posts
  • 58 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle







  • This is what’s so great about Linux, you can use whatever the hell you want.

    Flatpaks provide some cool security functionalities like revoking network access to a specific application. Maybe you care about this, maybe you don’t.

    My personal policy is to always install from the repos. Occasionally something is only available in flathub, which is fine for me. I really understand how hard is maintaining something for every single package manager and diatributions and totally respect the devs using a format that just works everywhere. If I were to release a new Linux app, I would totally use flatpak.


  • I’d just like to vent that these kind of discussions are one of the big turnoffs of the Linux community in general. People speak “in absolutes”.

    You either do it this way or you’re a dumbass. You either use the distribution I like or you’re doing it WRONG. You shouldn’t use Arch because you’re not experienced enough, you should use Mint for an arbitrary amount of time before you graduate to the good stuff.

    You friends get way too worked up over other people’s personal preferences and push your biased and subjective views as facts.

    Is Arch Linux the right fit for a newbie to Linux? The right answer is “it depends”, not “never”. Would I recommend Arch to my mom? No. Would I recommend it to my programmer colleague who already lives in the Powershell? Sure, why not.










  • Just go ahead and write a very basic working kernel in rust.

    I don’t get this stance, really. If I want to write a driver in Rust I should start by creating a completely new Kernel and see if it gains momentum? The idea of allowing Rust in kernel drivers is to attract new blood to the project, not to intentionally divert it to a dummy project.

    Rust is sufficiently different that you cannot expect C developers to learn rust to the level they have mastered C

    If you watch the video, no one asked anything from the C developers other than documentation. They just want to know how to correctly make the Rust bindings.

    Note that Rust is not replacing C code in the Kernel, just an added option to writing drivers.