• 1 Post
  • 70 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle






  • Efwis@lemmy.ziptoLemmy Shitpost@lemmy.worldLawrence
    link
    fedilink
    English
    arrow-up
    11
    ·
    1 year ago

    Trust me, it’s not just satire.

    I was in a homeless shelter about 7 years ago, unfortunately as a resident, and this dude I shared my room with was like 40 and would post on his Facebook profile that he was looking for a godly woman who doesn’t want to work and wants kids. His description of her was as follows:

    Must be blonde, 5 foot to 5.5 foot tall, weigh no more than 110 lbs, must be religious to the only point of life was serving god and him. She must be no older than 25 and big boobs and perfect breeding hips.

    This dude was 40, 300 lbs, 6ft tall. Took a shower once a week, worked at pilgrims chicken on the kill floor, and was so slow it took him 10 minutes to walk up a 100ft driveway from where the bus dropped him off. And yet he could never understand why No women wanted anything to do with him


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









  • And probably expensive as hell to boot. Although to be fair as an IDE it does work well. I can code just like I was in an IDE. It literally suits my needs when using python, rust or any other markup language. Even seems to do some autocomplete for me.

    I honestly thought they were the same really.

    The only stuff I miss is the way dreamweaver worked back in the day where you can see wysiwyg as well as the code. But that was yesteryear where adobe wasn’t as money hungry