• 102 Posts
  • 857 Comments
Joined 1 year ago
cake
Cake day: July 25th, 2023

help-circle
  • Navigation within a single workspace is pretty much the same as in Sway/i3.

    I don’t remember how it’s done in Sway/i3. If you have two monitors side by side, moving the focus from the left most window on the right monitor to the left, moves the focus to the left monitor.

    A major difference is the workspace design. In Cosmic, there’s currently a single set of workspaces for each monitor. In Sway there’s one set shared between all monitors.

    The workspaces can be either horizontal or vertical, which is useful depending on how you configure a multi monitor setup. This is because with vertical workspaces, moving down from the bottom window moves the focus to the next workspace (and vice versa).

    In my case with two monitors side by side, this is awesome, because moving the focus feels like moving naturally on a single giant plane. E.g. moving down moves to the next workspace, then moving to the left moves to the left monitor, where I could move up to the workspace above etc.

    It’s difficult to explain for me, so I recommend giving it a try (or maybe wait a while, depending on your needs, e.g. there’s no VRR, no window rules etc. Also, currently monitors have to be aligned at the top edge to be recognised as side by side. If they aren’t, moving between monitors and workspaces doesn’t behave right.).


  • I like the Cosmic tiling better than Sway, because it tiles through the long edge by default.

    I.e. If I just two windows after each other, Sway will tile them as two equal columns. If I open another window, it’ll add another column, while making each column the same size.

    Cosmic also creates two equal columns with two windows, but the next window tiles the focused column horizontally.
    With three windows this means half the screen is a single window, the other half is two windows taking up a quarter of the screen. Obviously if you instead focus another window, it’ll be tiled instead.

    This is basically the same behaviour as the autotiling script for Sway/i3, but it works reliably (I’ve always had issues with those scripts).



















  • I disagree with the notion that it’s better for the cheaters to have an easier time (and less chance of being detected), but you’re right, BattleEye doesn’t solve the cheating problem for GTA.

    Rockstar should fix their netcode and run game server on dedicated server, instead of their customers PC’s. I’d think decting aimbot isn’t the biggest issue, while cheaters are able to break entire lobbies…

    IMO no game should require client side anti cheat except for shooters, where looking through walls and aimbot is actually difficult to detect server side. At least for those is it possible to find valid arguments (except for being lazy).



  • tl;dr
    Read the first sentence after each citation ;D


    So Wayland, a protocol, is needing the addition of other protocols?

    Yes. What we know as Wayland is the Wayland core protocol and a few other protocols that are absolutely necessary for desktop use (stable).

    Then there is staging, which is not necessarily implemented by all compositors, e.g. fractional scaling.

    Unstable also exists, which is even easier to get a protocol into (idk the exact requirements, likely the amount of support and explicit dislike by contributors).
    These are often only used by a subset of compositors with e.g. XDG decoration allowing compositors to announce to clients (windows) that they support server side decorations (top bar with close/minimize/maximize buttons). This isn’t implemented by Gnome, but most other desktops support it.

    Different desktops also have their own protocols, which are published so that apps targeting those desktops can implement them. Some are also supported by other desktops, if they think they are suitable for them.
    E.g. wlr layer shell makes status bars possible, which are used by basic compositors like Sway or Wayfire. KDE also supports it, even though it was originally created by wlroots.

    Does this make it a Wayland Distro?

    In a way you could say that a compositor is a Wayland distro, as it implements a subset of Wayland protocols.

    In the end this is good, because it allows for rapid development and discontinuation of protocols. E.g. if a better protocol comes around, both protocols can be supported at the discretion of every compositor.

    The goal was to solve the problem of X11, where Xorg still has to support drawing UI by itself, even though no program or toolkit uses it anymore (the 80s were very different). The Wayland core is so minimal there shouldn’t be any issue with using it for a very long time.

    Also, Wayland was developed by people with the goal to use it in automotive and other industry applications, where basic desktop functionalities, like multiple windows or session lock, aren’t useful.



  • I like the Moz://a branding, altough most people wouldn’t get it, so it makes sense to switch to correct spelling.

    Whether the T-Rex is the coreect choice, is another question. I do like that it feels more creative than the basic, reduced logos of today.

    Edit: I do like the new Logo. It looks good and it does match its “activist spirit”. Mozilla the corporation is different from the foundation, and I do believe, that Mozilla is closer to its roots than all other browser vendors - including the reskins of Chromium.


  • Blender and DaVinci Resolve work better on Nvidia. AMD might work, but it will be a hassle and you’ll likely need the proprietary AMD drivers anyway.

    With Nvidia supporting Wayland and the open-source NVK continuing to get better, you could even switch to open source drivers for gaming at some point, if you prefer.

    Edit: I’ve had enough issues with AMD GPU’s clocking down while gaming, leading to micro stuttering. So don’t buy AMD just because everyone tells you they work flawlessly.

    For CPU and mainboard, everything works well — just don’t buy a random unknown SSD from Amazon, then you’re asking for data loss and random issues.