• 12 Posts
  • 208 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle



  • I used the Xbox 360 game controller for years on PC, then switched to Xbox One, then Xbox One S and then to the Xbox Series S controller. So we speak about decades at this point. I played extensively Steam games and emulation for all kinds of systems (where input latency is extremely important in some games). At the same time I also have used extensively a wired classic SNES like shaped controller that is wired connected and recently I replaced my Xbox controller with a 8bitdo wireless controller.

    So you see there is some experience in using and in comparison. Latency was never an issue and I never felt it. But the common theme here is, I never used Bluetooth and always use the (even if its proprietary) dongle by Microsoft for connection. That’s because it should provide superior connection stability and better input latency. I always had issues with Bluetooth before (I mean with any other kind of hardware connection) and always hated it and avoid it.

    Having said this, Bluetooth can be good. In example the Playstation consoles and their controller are using Bluetooth and its not an issue there. But you have to make sure that the driver and the Bluetooth dongle (or chip) is compatible and working fine, in combination with the controller. If you notice a difference between wired and wireless, then its a sign that the wireless connection doesn’t work properly for your setup. I think my best advice is to buy the proprietary dongle from Microsoft (as I hate doing this, but its the best for Xbox controllers). You will also need to change the driver from xpadneo to xone.

    However I switched recently to a different controller because I experienced a few issues with the driver. Because the driver wasn’t updated for a while and it broke with a new Linux Kernel update on my Archlinux based system.



  • (Edit: I always mix up the terms server side and client side decoration. Hopefully by my description its clear which one I’m referring to.)

    Pro SSD: the window manager should decide how the apps look

    • user: consistency across the operating system usage
    • dev: generalized and less burden on the dev, less dependencies to worry about and development specific to GNOME
    • both: flexible, change your window manager and the app changes without modifications (at least in ideal world)

    At least for a normal window. I wouldn’t mind if an application can request with a high priority that it wants to display its own decorations. In that case there should be an option to disable decorations from the window. That is how some applications do work and allows for a flexible usage based on users configuration. Now if there was just an official API from all window managers that can check this configuration, then the user wouldn’t even need or know there is a setting for.








  • The best would be to ask a Gentoo user. :D

    Disadvantage (besides the update procedure mentioned by the other answers here) is, it might take lot of time, download lot of dependencies and files and need additional space on your drive to compile. It can be a hassle to install and setup the required tools and libraries too. This highly depends on the project itself if its worth it. In example nobody in their right mind wants to compile their web browser (Firefox, Chromium, whatever) themselves (sorry if I offended someone with that. :D). But a simple and short C program is as simple as running make command in example (given the dependencies are installed, which are most likely for simple programs after a few programs have been compiled).

    Most of the time you don’t need to compile software. Especially if you trust the source or its in the official repositories of your distribution.

    Can it mess with my system in any way?

    Depends on what you mean by that.


  • I still use my mouse with Krohnkite. I even move a window over another, to swap their positions, or change their size with my mouse. It’s not like using an auto tiler means no mouse usage.

    KDE wants users to use the mouse.

    We are not in GNOME here. KDE team does not want users to use their mouse. KDE usually is there for configuration and features, so that users can do whatever they want. I still think in a future the KDE team will implement “proper” auto tiling functionality.

    I watched talks and discussions with Nate Graham. And yes, its obvious they don’t use auto tiling and don’t understand the benefit from it. That’s why the compromise they builtin is the way it is. But as time goes on, more tiling fans will arise, even GNOME and upcoming COSMIC have auto tiling builtin. There are working scripts to auto tile.

    KDE will have builtin auto tiling functionality. It’s only a matter of time.




  • I switched from a Qtile tiling window manager to KDE with Krohnkite. It does the job of handling the windows. The auto tiling aspect is the only thing I miss in any regular window management. The reason why I switched to KDE back then was, a problem with Qtile and because KDE was good on the Wayland front. In fact, it was the only viable option in my opinion for a desktop environment. I was also using lot of KDE applications anyway, so it made sense.

    Cons: you have to use KDE with Krohnkite

    I don’t see this as an con. Maybe you could argue that Krohnkite is not a core system functionality and we rely on some community member. BTW that was the biggest issue why I switched away from GNOME years ago, because too much core functionality was community dependent (and breaking). The KDE team themselves should integrate such a functionality. Auto tiling reaches was never more popular and KDE itself has some tiling functionality builtin, just not auto tiling.

    Like Qtile had, I like we have many layouts to choose and cycle from. My 4th desktop is set to everything float; no tiling. I could not stand a auto tiler that has only one builtin layout logic.

    But there are some couple problems using Krohnkite. It’s not as configurable as I am used to with Qtile off course. And getting rid of the borders and having colored borders in KDE for focused applications and such, was a pain to setup. KDE really need some builtin functionality for that.


  • The thing is, Valve wouldn’t even need to open source the client. If there was an official programming interface as an API to connect to (with online checks to verify off course), then people could build their own clients. The cool thing would be, only features they want to have and with the GUI toolkits and interface the way they want it could be possible. Totally open source too, at least on the client part. Maybe the official API and client could only do some stuff, not everything; in example selling or trading items or buying games would be not possible, but stuff like starting a game. This alone would be awesome.