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

help-circle
rss

  • On MacOS and some desktop environments like Unity and optionally in Plasma, there’s a UX design pattern called the “Global Menu”. At the top of the screen, as part of the desktop’s shell, there’s buttons labelled File, Edit, View, etc for you to interact with.

    Firefox is seemingly (I haven’t tested it myself, not using Plasma) enabled this functionality under Linux. Previously it required a patch to work. But this functionality has always existed on the MacOS version.














  • I run Fedora Silverblue on a N100.

    It’s very usable. For most actions, it feels pretty similar to my much more powerful desktop. but has some limitations.

    • I am able to run two 1440p monitors at 144hz via HDMI, but the screen occasionally blacks out for a second due to HDMI limitations. Running at a lower refresh rate should avoid the issue.
    • Gnome shell animations aren’t running at 144hz, even with triple buffering (never tested if it maintains 144hz with just one monitor at 1440p). Haven’t tested KDE.
    • I am able to comfortably run Minecraft with 60+ fps with performance enhancing mods, though at like 5 chunks rendering distance. Honestly it’s fun to play this way, feels nostalgic. Though performance will dramatically drop if you try to play a video at the same time, though dropping it to like 480p or even 720p helps a lot.












  • I use Silverblue and MacOS daily, I enjoy the former so much more.

    Unfortunately my relatively new Lenovo laptop has a small but also major driver bug that hasn’t been fixed in all the time I’ve had it. Bad to the point I got the Mac to have actual working hardware. But I do not enjoy MacOS in the slightest. At best I can say it harasses you less than Windows and respects the user a few degrees more than Windows.










  • Wasn’t vertical integration, was done by packager.

    We don’t believe that the openSUSE Deepin packager acted with bad intent when he implemented the “license agreement” dialog to bypass our whitelisting restrictions. The dialog itself makes the security concerns we have transparent, so this does not happen in a sneaky way, at least not towards users. It was not discussed with us, however, and it violates openSUSE packaging policies.





  • Ah I had the same issue. JavaFX still uses X11. By default VSCode only lets X11 be used if Wayland is not available (this is the X11 fallback permission). Disabling X11 fallback will let VSCode use Wayland and let JavaFX use X11. I might make an issue for this on the flatpak’s GitHub asking for this change.

    Honestly, the truth is that setting up containers for development will always be a hassle. My low tech way is just to make a distrobox container with its own home folder, install an IDE in it, and install packages. The more proper way to do it would create your own containerfile to build your container for developing.

    VSCode also has its DevContainers extension but that doesn’t work in VSCodium and does some weird things.