• 0 Posts
  • 24 Comments
Joined 2 years ago
cake
Cake day: July 5th, 2023

help-circle
  • kewjo@lemmy.worldtoSelfhosted@lemmy.worldDocker Backup Stratagy
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    5 days ago

    caches are never really a concern to me they will regen after the fact, from your description i would worry more about db, this is dependent though in what you’re using and what you are storing. if the concern is having the same system intact then my primary concern would be backing up any config file you have. in cases of failure you mainly want to protect against data loss, if it takes time to regenerate cache/db that’s time well spent for simplicity of actively maintaining your system




  • kewjo@lemmy.worldtolinuxmemes@lemmy.worldNo bloat
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    5 days ago

    in Windows you separate each drive by a letter like C:, D:, etc, however on Linux your drives are mounted as part of your folder structure. the top level is called root which would be / you can then mount each disc as a folder under root, so for example /home could be a separate hard drive but it’s still mounted under root, note the starting slash. This means the command deletes any and all files+directories under root, this can include mounted USB, mounted network drives and anything mounted to your root. you’re basically nuking all the files you can access when you’re logged in as admin/root.





  • there was a study done in the 50s that pretty much decided US health policy for decades that said fat is bad and makes you fat. the reaction to this was for companies to remove fat from their products to claim it’s low fat but in order to maintain taste they replaced it with sugar. this proliferated all food products and being coupled with both parents working 40+ hours a week caused a lot of families to fill fridges with highly processed foods with “healthy” sugar/fat levels that could be prepared easily. tie in the fact that there’s no time to exercise with the fact that most Americans drive to destinations, it becomes easy to read articles that x is the cause of obesity that it took a long time to realize what the real problems are.







  • flatpak distribution is generally done by the developer as a common packaging method. if a distribution wants a native install it’s up to package maintainers of the distribution to support the application. although the package maintainers have to make sure they’re packaging the right versions of dependencies which becomes a problem known as dependency hell.

    in your example of handbrake it’s true the main application is pretty small but that’s because it relies on libraries and is a wrapper for ffmpeg. even if you install through a package manager you still need to compare the total size of dependencies.

    the disc space usage becomes a problem due to installing libraries both natively and in sandbox. however if you keep a relatively small system install and install applications through flatpak the disc usage will be pretty negligible. if disc space is really a concern then using something like btrfs with compression+dedup would probably solve most problems.


  • it’s great for applications that are notorious for requiring specific versions of libraries and can cause dependency hell. moves unnecessary system dependencies into a sandbox. for me this means i don’t have to enable multilib to install Steam and pull in 32 bit libraries on my root.

    while it does take a lot of disc space it doesn’t duplicate dependencies in most cases. i would say you receive some good benefits at the cost of a bit more disc space, such as increased security, easy installs, explicit app permissions. it’s great for when you have to install a proprietary tool in that you gain control of what it’s allowed to access.



  • given how many targets are supported by llvm there’s really little difference in cross platform support asides from building artifacts for the specific target platform. wrapping package delivery in a package manager removes the additional complexity to the end user.



  • Maybe they could white label a password manager (Bitwarden?)

    not sure starting at which version, but in android you can set bitwarden as a default password manager system wide which integrates pretty seamlessly with firefox and other apps. only place i know bitwarden doesn’t really integrate well with firefox is on Linux but that seems more due to bitwardens lack of interest to implement freedesktop apis.

    i agree though with additional revenue streams, they need to break dependence on Google search engine revenue. maybe spend research on alternative monitization to ads and sponsored content that could be implemented at a browser level and split revenue between browser and websites.


  • you seem to be blaming the workers for turning out flops but in general it’s the managements lack of planning and micromanagement that’s the general cause.

    no one who’s a developer, artist, designer wants to add micro transactions, that comes from top down because it’s a revenue generator. they want to polish the games so they can be proud of the work, but are not given time.

    executives are not the ones generally being let go and the ones that are will be cashing out from the acquisition. expect those IPs to get worse and have more enshittification because that’s what makes money and that’s all corpos care about.

    you don’t get a larian studios from laying off talent, you get it from good management and giving your talent time to deliver.