• 0 Posts
  • 335 Comments
Joined 2 years ago
cake
Cake day: June 30th, 2023

help-circle





  • The planned obsolescence is most likely a deliberate trade off rather than actual planned obsolescence.

    If fast charging did do significant damage to battery life and this was known at the time of implementation, the decision would have been “users want fast charging phones” Vs “users want devices that last a long time”.
    In this instance, the convenience of fast charging absolutely would have won.

    “Users want a clear and easy to use device” Vs “users want a robust device”. Which is why we all have glass screens, and the glass technology had to catch up to further expectations.

    “Users want easy wireless connectivity” Vs “users want fast and reliable network speeds”. WiFi wins, and has to catch up to further expectations.







  • I installed endeavouros on my windows laptop.
    The installer guided me through the partitioning, setting up systemd-boot, and it was all great.
    I had to disable bitlocker in windows (not that bothered about) and secure boot in bios (also not that bothered about).

    Ran smoothly dual booting both for about 4 months.
    Then a windows update hit, and fucked the boot.

    Thankfully, this is a common enough thing that there are plenty of tutorials out there.
    A liveUSB of endeavouros, some tinkering, and I was back up and running.

    The cause seems to be FastBoot, where windows keeps the boot partition mounted. What I think happens is that bios tries to read the boot partition, which is configured/loaded for windows (because it never cleaned up after itself due to FastBoot being on) and boots into windows.
    Since turning off FastBoot, I haven’t had any issues in the past 8 months.




  • https://store.steampowered.com/steamos

    Does this mean I can install SteamOS on any device? We expect most SteamOS users to get SteamOS preinstalled on a Steam Deck or device that incorporates SteamOS. The only devices officially supported on SteamOS right now are Steam Deck and Legion Go S. We are working on broadening support, and with the recent updates to Steam and SteamOS, compatibility with other AMD powered PC handhelds has been improved.

    If you are interested in installing SteamOS on your device and providing feedback, you can follow the instructions here.

    here links to https://help.steampowered.com/en/faqs/view/65B4-2AA3-5F37-4227

    With instructions to install steamos and the note:

    Currently, the only devices officially ‘Powered by SteamOS’ are Steam Deck and Legion Go S. We are working on broadening support, and with the recent updates to Steam and SteamOS 3.7, compatibility with other AMD powered PC handhelds has been improved.

    So, it’s unlikely to be smooth sailing. But it can be done, and steam is working on improving it.

    There seems to be some forks out there that claim to improve desktop installation, but I have no idea how active or decent they are.


    Personally, I think steam is missing a huge market slice by not creating a steamos for desktops.
    However, they don’t need it and probably don’t want it. It’s a market slice in a market they don’t need or want: operating systems.
    People that would use it likely already have steam on windows. So, it’s not bringing in new customers (like the steam deck does).
    People that game on Linux likely already use Steam Proton (which is an amazing contribution). So, no new customers by distributing a whole desktop OS.
    It’s starting a fight with Microsoft (which I think we all want), but with no real benefit to Steam.

    I think steam is smart to stay in their lane of handheld OS and Linux tooling for gaming.
    Let the desktop gaming distros be maintained by other people. Ideally steam would support those distros, but just maintaining Proton and generally pushing Linux gaming is still a huge contribution.






  • especially once a service does fail or needs any amount of customization.

    A failed service gets killed and restarted. It should then work correctly.
    If it fails to recover after being killed, then it’s not a service that’s fully ready for containerisation.
    So, either build your recovery process to account for this… or fix it so it can recover.
    It’s often why databases are run separately from the service. Databases can recover from this, and the services are stateless - doesn’t matter how many you run or restart.

    As for customisation, if it isn’t exposed via env vars then it can’t be altered.
    If you need something beyond the env vars, then you use that container as a starting point and make your customisation a part of your container build processes via a dockerfile (or equivalent)

    It’s a bit like saying “chisels are great. But as soon as you need to cut a fillet steak, you need to sharpen a side of the chisel instead of the tip of the chisel”.
    It’s using a chisel incorrectly.