• 9 Posts
  • 89 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle






  • I’ve been on Linux for 20+ years and have never had to rely on paid for support. The paid for support is really geared towards professional big business work stations and server stacks. If you need support for Linux you can find free support on their forums 99% of the time. It’s the IT departments with lazy techs that rely on Linux paid support.

    You are right about the Micro$uck hate though. Why should I pay to use an operating system on a computer I buy and use until it’s reached it’s EOL when I can use Linux to do everything you do on windows and I don’t have to pay for the software? In today’s economy, it makes sense to use Linux.


  • The creators are making money from the ads, they probably won’t abandon ship at yt unless they stop making revenue. A lot of the creators on yt rely on the ads to be worthwhile in creating the content.

    I agree, yt is getting stupid with their ads, from what I understand they are now including ads in the yt premium subscription aervice, which is supposed to be ad free mind you.

    As long as greed dictates content, creators won’t abandon ship, unless they can have ads on the alternatives to make money on.


  • It’s a KWin scrip called Autocompose. Does endeavour ship it by default?

    Endeavour installs a mostly default DE when you make your choice of which one to use, so most of the DE’s come as packaged by the devs. If I’m not mistaken Autocompose is a default script included with KDE.

    I say mostly, because some parts of the DE you use is incompatible with the Arch ecosystem and disabled by default. For example, Discover on KDE is pretty much unusable on arch/EndeavourOS because the repos aren’t adequately designed for such a setup.


  • So do snaps and flatpacks. And they are still consider containerized / sandboxed. Appimages are the predecessors to snap and flatpack. The only difference is unlike Appimages they got it right for the most part.

    Generally speaking the Appimages integrate with KDE better than all the other DE’s. The codes for Appimages are still containerized from the OS in general as defined in my last post.



  • The thing about snaps and app image is they are containerized. The idea behind that is to help keep the apps separate from the main file subsystem by sandboxing them from each other as well as not cluttering your hdd with different versions of the same libraries to make them work.

    Because of the sandboxing, once you close the app it stops running in the background therefore there is nothing to get notifications from.

    IMHO, this is why snap and app image programs are not advisable for programs you may need notifications from on a, generally, required/needed basis.

    As for superconductivity, the only way around that problem is to download from source, compile it and let it run natively on your system in the background, or add it to you auto startup list so it is running at boot time.