• 1 Post
  • 34 Comments
Joined 1 year ago
cake
Cake day: August 12th, 2025

help-circle


  • Seconding that. I’ve just read through the website. Got interested. Then my eyes went to the top panel again finally, I’ve read “GitHub”, and my thoughts are “Huh? But this mismatches the rest of the page, especially with the AI stance and some push for simplicity combined with competence.”. Went back here to write about it.

    /me a ~10 year old ArchLinux user (using Arch for this long, my Earth age nobody cares about including me anyway). I’m thinking if I wanna actually try this for real. I currently have manually written packages that define the OS dependencies and configuration, and I don’t like the mutability of everything, the default update handling of no-longer-dependencies, the .pacnew… I still like and appreciate Arch obviously, but the pain points connect.



  • vas@lemmy.mltoLinux@lemmy.mlBan Windows at schools
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    14 days ago

    I disagree. While it would be correct in some way, it would be a different political movement.

    With “let’s introduce Linux”, it’s easy to stop mid-way and too early. For example, at 1 hour per week for 1 semester once during the whole school.

    With “ban Windows [from school computers and as mandatory software]”, the political agenda is clear and the technical goal is clear. And the benefit is clear, too.


  • vas@lemmy.mltoLinux@lemmy.mlBan Windows at schools
    link
    fedilink
    arrow-up
    39
    arrow-down
    1
    ·
    14 days ago

    That actually makes a lot of sense, if you remove concepts such as “but Windows is already customary here” from your head. From scratch, you’d never want to do this.

    If such a petition exists for the Netherlands or EU-wide, I’d sign and subscribe/support.





  • Sounds interesting! And welcome to Lemmy if you’re a new user indeed! (Otherwise, cheers.) Few personal thoughts below.

    Atomically upgradable images and the added security sound interesting to me. I’m not specialized enough to say whether that’s really going to help for my threat model, personally. I mean, in /boot I currently only have the Linux images. Verifying those seems sufficient, because the actual system is only decrypted afterwards when I enter my password.

    I must also say, accepting a concept is harder for me if the proposed line of thought is “GNOME OS is to be loved, and %project_name% is a bit like that”. Because personally, I remember Gnome since version 2 and I dislike what they’ve done with the system since. I only use gnome-disks from the entirety of them. From KDE I use more (kate), and from XFCE I use way way more. And I also dislike how GNOME pushed systemd onto all of us as a hard requirement. Not that systemd is necessarily bad, but the push for it didn’t feel right.








  • Adding to the comments about VIA and QMK, you can also use something on the computer itself to do ergonomics tricks and making F7 usable again.

    I’m in particular using kanata, which then works on everything from notebook keyboards to custom ones. I’m not 100% happy with it and in fact considering to write my own software for this, but it’s good-enough for basic usage. It might be good-enough for you. kmonad is less buggy but has fewer features (definitely enough for F7 though).




  • My personal basic tools for learning:

    • man bash. That’s the documentation for everything. It’s very careful and serious though, so sometimes you need…
    • Search in internet if you think your particular question is very “repeatable”. Stackoverflow used to be good, but now they’re all “AI AI AI by the way have you heard about AI?”. So I’m not recommending it anymore. For “advanced bash” there are pages that go over those “advanced topics”, too!
    • Run shellcheck to read your code and give suggestions/warnings. It’s a great tool for learning, too, besides the primary goal of reviewing code to be production-ready.
    • Sometimes, with extreme care, ask an LLM to review your code or give siggestions. It tends to hallucinate a lot, makes up wrong and unexisting stuff, but sometimes it’s useful, too. Especially at finding bugs. Again, it can be useful, but use with care. Oh, and it can actually be great at explaining, too. Throw it some syntax/code and it’ll explain wtf is going on. This part is very reliable and good.

    At my current level of experience I need mostly man bash, and occasionally all of the rest. Before I used a lot of stackoverflow and simply thinking of what I even want.