• 0 Posts
  • 54 Comments
Joined 10 months ago
cake
Cake day: June 24th, 2024

help-circle


  • Well… Yes, Steam has a (very stupid in my eyes) policy of “if the developer puts up an update, then everyone must update” but that is not (fully) invalidating my point.

    The content of the update and the time of release of the update is still outside of Steams responsibility. If the developer decides to push an update that uses some crazy stuff that works fine in Windows but would need some obscure codepath that are not available in Wine/Proton and by that rendering a game with a “Great on Deck” rating to “unplayable” then there is nothing Steam can do about it. Or if the developer patches in some DRM that will not run on Linux. Well, yes they could put up some lines in the terms of contracts for the developers to disallow this kind of changes but i am sure this would not end well at all.

    Another thing, that most likely could even less be regulated, would be if the developer pushes an update that changes the UI to something that looks great on a huge screen but is unreadable on the SteamDeck.

    Yes, all this would be way less an issue if Steam would make updates optional or would allow (an easy way) to choose the version. So i am totally on your side with that point.









  • Unreal Tournament 2004 depends on SDL 1.3 when I recall correctly, and SDL is neither on Linux nor on any other OS a core system library.

    Binary only programs are foreign to Linux, so yes you will get issues with integrating them. Linux works best when everyone plays by the same rules and for Linux that means sources available.

    Linux in its core is highly modifiable, besides the Kernel (and nowadays maybe systemd), there is no core system that could be used to define a API against. Linux on a Home theater PC has a different system then Linux on a Server then Linux on a gaming PC then Linux on a smartphone.

    You can boot the Kernel and a tiny shell as init and have a valid, but very limited, Linux system.

    Linux has its own set of rules and his own way to do things and trying to force it to be something else can not and will not work.


  • It works under Windows because the windows binaries come with all their dependency .dll (and/or they need some ancient visual runtime installed).

    This is more or less the Flatpack way, with bundling all dependencies into the package

    Just use Linux the Linux way and install your program via the package manager (including Flatpack) and let that handle the dependencies.

    I run Linux for over 25 years now and had maybe a handful cases where the Userland did break and that was because I didn’t followed what I was told during package upgrade.

    The amount of time that I had to get out of .dll-hell on Windows on the other hand. The Linux way is better and way more stable.



  • A new homepage for the business of my wife.

    I plan to use Hugo for it, I just wish the documentation would be better.

    For the homepage I need a few additional “non-blog” pages and from the documentation I am not sure how to do that the best way.

    But to be honest, I have not really looked deeper into that, so it is very possible that I just missed something.