• 1 Post
  • 22 Comments
Joined 16 days ago
cake
Cake day: June 13th, 2024

help-circle








  • Amanda@aggregatet.orgtoTechnology@lemmy.worldWhy we don't have 128-bit CPUs
    link
    fedilink
    English
    arrow-up
    37
    arrow-down
    1
    ·
    6 days ago

    The comments on this one really surprised me. I thought the kinds of people who hang out on XDA-developers were developers. I assumed that developers had a much better understanding of computer architecture than the people commenting (who of course may not be representative of all readers).

    I also get the idea that the writer is being vague not to simplify but because they genuinely don’t know the details, which feels even worse.







  • I’m kind of souring on Fedora Kinoite. I generally sometimes pop in to try how Linux is doing, and I had great hopes for KDE Plasma 6 and immutable distributions for stability. However, I’ve found that many things in the UI are still wonky and broken, fonts don’t render well, and I keep running into limitations in the flatopak/containers ecosystem.

    Here are a few paper cuts:

    • I can’t get the launcher to do web searches despite them being available and configured, even when manually invoking the keyword
    • fonts look blurry and render weirdly; all of the household macs produce ok output on the same screen so it isn’t the issue
    • I really miss having consistent emacs text navigation bindings but shortcuts like C-a/C-e are already taken and remapping is difficult to get to work consistently
    • I’ve been trying to compile parts of the Linux minidisc system but the dependencies aren’t available outside of a toolbox and USB isn’t available inside. I think, it’s difficult to google and I’ve time boxed trying to fix it to N hours and exhausted those, so it’s either impossible or too difficult
    • for a long time Obsidian (from flatpak) couldn’t agree with the window manager to draw drop shadows and window decorations which meant that figuring out where obsidian ended and the white window underneath it began was literally impossible
    • sometimes the wired USB keyboard stops working if I unplug it and doesn’t start working until I’ve plugged it in/unplugged it a few times




  • Lots of bad answers here. Obviously the kernel should schedule the UI to be responsive even under high load. That’s doable; just prioritise running those over batch jobs. That’s a perfectly valid demand to have on your system.

    This is one of the cases where Linux shows its history as a large shared unix system and its focus as a server OS; if the desktop is just a program like any other, who’s to say it should have more priority than Rust?

    I’ve also run into this problem. I never found a solution for this, but I think one of those fancy new schedulers might work, or at least is worth a shot. I’d appreciate hearing about it if it does work for you!

    Hopefully in a while there are separate desktop-oriented schedulers for the desktop distros (and ideally also better OOM handlers), but that seems to be a few years away maybe.

    In the short term you may have some success in adjusting the priority of Rust with nice, an incomprehensibly named tool to adjust the priority of your processes. High numbers = low priority (the task is “nicer” to the system). You run it like this: nice -n5 cargo build.