she/they

  • 0 Posts
  • 16 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle



  • Oinks@lemmy.blahaj.zonetoLinux@programming.devThe Wizard and His Shell
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    3 months ago

    GUIs do have advantages in things like discoverability. Honestly the 1983s Apple Lisa nailed this with the idea of having clickable menus annotated with keyboard shortcuts, so users could do the same thing faster next time. For some reason we stopped doing this (especially in web apps), but that’s a reason to make better GUIs, not to RETVRN to the feature set of a VT100.

    I don’t know why we have to go on nonsensical diatribes about “UNIX wizards” though when we’re fundamentally talking about a handful of minor UI improvements to things that already exist.


  • It depends a lot on which specific GPU you have and whether it’s a laptop.

    New-ish GPU in a desktop with the monitor plugged directly into the GPU? Easy to get working, literally a checkbox on most distros.

    1000 series GPU or older in a laptop and you need reasonable battery life and/or some “advanced” features like DP Alt-Mode? Good luck.

    Edit: Also, no Wayland until very recently. Possibly never, depending on the age of the GPU.


  • It’s wild how on the orange website I can read entirely sensible discussions about tricky Bash semantics or whatever, while people in a parallel thread are seriously arguing the Trump admin’s repressions are dwarfed by… whatever “repressions” they think happened during Covid. And I don’t even click on the threads about disabilities (especially autism) anymore because it’s so predictably sad.


  • Yeah some people seem to have this expectation that there should just magically be a button to unbreak the PC. They talk about their personal pain points when using Linux as if there’s a conspiracy of devs to hide the unbreak buttons for the sake of elitism, but that… just isn’t a thing? If it was that easy to fix an issue, you probably wouldn’t need to fix it because the system would already come unbroken by default. I sympathize with everyone’s Bluetooth configuration woes but mostly it’s a pain in the ass because Bluetooth, in general, is a pain in the ass, not because of elitist devs (who I should mention are doing this in their free time for no pay. There’s almost no money in desktop Linux, unlike in servers).


  • kwriteconfig6 is barely documented because you’re not really supposed to use it. All of the settings that users are expected to change are in the nice settings app that Plasma ships with. Using kwriteconfig (or equivalently a dconf editor on GNOME) is like editing the registry on Windows; you are implicitly opting into more power, out of most guardrails and into potential breakage. The UX being a bit questionable (though honestly it’s really not as bad as you’re saying, it does exactly what it sounds like it will do?) is to a degree intentional, because you’re not supposed to be using this unless you know what you are doing.


  • To be fair that’s not the entire story, since you need to actually resolve the conflicts first, which is slightly scary since your worktree will be broken while you do it and your Linter will be shouting at you.

    You may also want a dedicated merge tool that warns you before accidentally commiting a conflict and creating a broken commit.

    Oh and non trivial resolutions may or may not create an evil merge which may or may not be desirable depending on which subset of git automation features you use.

    Using git status often is definitely good advice though.


  • The GDPR conversation is hilarious. Sure they’re a US based company, but after 5 years of operation I would’ve expected them to have consulted a lawyer about this at some point. Forgetting (assuming it’s not “forgetting”) about the required documentation is not the worst thing in the world morally but it doesn’t exactly make them look competent either.




  • Does your script fork at some point (and might exit before the rsync job is completed)? Because then you need to use Type=forking instead of simple or oneshot, otherwise systemd will start trying to clean up child processes when the script exits.

    Edit: Actually considering the time span involved Type=forking will not solve your issue because it will timeout, if this is the problem you need to change your script to not do that.




  • While unfortunate, not shipping these standard Google apps is not really an option for any Android manufacturer due to Google requirements. Including them is required if you want to use anything from the GSM, which includes things like the Play Store and everything it touches. You can technically ship a different Android distribution like Lineage or /e/, but that’s not really what most people will be expecting of an “Android” phone and will narrow the viable target demographic even more than the value proposition already does.