• 25 Posts
  • 33 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle

  • That laptop setup is actually insane. I love the “roleplay” he had set up for it, making it seem like a computer used at a nuclear reactor (though the more realistic setup would have been to install Windows XP with default background).

    Also funny to see him doing more complex things like setting up a systemd service to hide and show waybar dynamically.






  • This is overly complicated. Just install Java then run

    flatpak --user override --env="FLATPAK_ENABLE_SDK_EXT=openjdk" com.vscodium.codium
    

    Note this works for all other SDKs too. It works especially well for programming languages like Rust that have their own package manager.

    Doesn’t work so well for languages like C/C++ where you use your distro package manager to install dependencies. In those cases it’s easier to install VSCodium inside a container where you do have access to a distro package manager.




  • Leaflet@lemmy.worldtoProton @lemmy.worldPhotos in Proton Drive
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    12 days ago

    The fediverse is not private. It’s open, that’s the point of it. There’s very few protections on your data. By necessity, your data will flow through hundreds of third party servers who can do whatever they want with it.

    The benefit of the Fediverse is that it’s decentralized and that helps users avoid the BS that Twitter went through.







  • I haven’t watched the video yet, but keep in mind “resource usage” being lower isn’t always better.

    For example, Plasma had an issue for some people where animations would not happen, freeze the system momentarily, and stutter. The reason why turned out that these people were using slow drives. Plasma was trying to load the bytecode for the QML animations from disk, but the IO operation took too long so the animation suffered. Had this bytecode been stored in memory, the performance would have been better.

    But I also don’t want to discount the fact that some (perhaps most) of the time, high resource usage is a bad thing caused by poor programming and using technologies that are heavier, like Electron. Whether those tradeoffs are worth it are another matter.

    I wish more developers actually used their software low-end devices to find performance issues. I recently got an Intel N100 and it’s actually been a decent experience on Linux, though Gnome shell’s animations are a bit stuttery even on Gnome 48. Haven’t tested any other desktop though.