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

help-circle

  • Efwis@lemmy.ziptoAsk Lemmy@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 months ago

    Unionize. Have companies pay you fairly for what you do.

    The problem with that here I. The states are two fold. First of all if the companies could, at least here in the states, they wouldn’t allow unionization. They don’t want to pay fairly for what you do. All these companies want to do is make as much money as possible, while paying the workers as little as possible.

    Most of the companies here would like us to work until we die on the lines, but pay us nothing to do the work so they could make it all. Companies don’t give a damn about workers rights, or being fair to us. A lot of non-union shops will fire you for trying to bring a union in. They would be extremely happy if the labor boards, OSHA etc would cease to exist.


  • Efwis@lemmy.ziptoPrivacy@lemmy.mlHow long does it take to build LibreWolf?
    link
    fedilink
    English
    arrow-up
    21
    arrow-down
    1
    ·
    3 months ago

    First, this would be a better question to ask in a Linux specific community.

    Second, Build time is really subjective to the computer and its hardware. There could be bottlenecks at the cpu/memory from the motherboard that will slow it down. It also depends on whether you’re spinning rust or using an ssd.

    There are a lot of factors involved in the whole that makes it hard to definitively say how long something takes to build.




  • To this day the government is still trying to create a lot of the tech from Star Trek. They are actively working on warp technology, replicators for food and clothes etc and Star Trek was the basis for a lot of today’s computers (i.e. no tubes like old tvs and computers before the invention of the desktop computer).

    One time the government actually approached the producers and wanted to know how they got the doors to open and close automatically like they do. Genes answer “there’s two men holding onto broom sticks, one on each side, when the actor walked up to the doors they would pull the broomsticks and make a ‘whooshing’ sound as they opened and closed them “

    Now we have that tech on 90% of retail shop doors. Star Trek was the basis for a lot of tech we use now.




  • 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.



  • 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.