• 0 Posts
  • 196 Comments
Joined 4 years ago
cake
Cake day: June 28th, 2020

help-circle




  • #!/usr/bin/env dash
    
    set -e
    
    cd $HOME/nixcfg
    
    # flake inputs to update
    for input in nixpkgs nixos-hardware home-manager hosts; do
    	nix --extra-experimental-features flakes --no-warn-dirty flake update $input
    done
    
    # rebuild NixOS
    nixos-rebuild --use-remote-sudo switch --keep-going --fallback --flake $HOME/nixcfg#$(hostname)
    
    # check for firmware upgrades
    fwupdmgr get-updates
    
    # print hard drive status info
    sudo smartctl -H /dev/nvme0n1
    sudo zpool status -v -x
    






  • There are several browsers that can operate with low memory requirements, but you have to be willing to live without JavScript & the front-end needs to have been built with accessibility & progressive enhancement in mind. …Which most front-end developers don’t do & the industry doesn’t normally pay them enough to care or get better results (& following YouTube tutorials always tells you to use the latest bloated framework which is overkill for your project).

    Also Fedora doesn’t ship with LTS kernels which makes me question their package management strategy.



  • Correct me if I am wrong, but my understanding is that you use Coq to prove your theroem, then need to rewrite it in something else. I think there is some OCaml integration, but OCaml—while having create performance for a high level language & fairly predictable output—isn’t well-suited for very low-level kernel code. The difference in the ATS case (with the ML syntax similarity 🤘) is you can a) write it all in a single language & b) you can interweave proof, type, & value-level code thru the language instead of separating them; which means your functions need to make the proof-level asserts inside their bodies to satisfy the compiler if written with these requirements, or the type level asserting the linear type usage with value-level requirements to if allocating memory, must deallocate memory as well as compeletly prevent double free & use after free.

    For those in the back: Rust can’t do this with its affine types only preventing using a resource multiple times (at most once), where linear types say you must use once & can only use once.







  • More appealing? Linux runs basically all server infrastructure where even Microsoft bent the knee for Azure & Windows Subsystem for Linux. If we are talking about Desktop Linux, it will remain popular with those building software for easier/better dev tooling & wanting to better understand the systems their production code is run on. As software becomes more intergral to our lives & knowing how to write/debug it rises, folks will slowly keep trickling in as the have for decades where more & more software is treating Linux (& the web, & since BSDs, et al. are running similar software such as GTK they are also included) as a primary target. The other desktop OSs continue to shoot themselves in the foot injecting ads into the OS or denying system-level access to the machine you own.

    A would say a better focus is mobile Linux… as casual users have migrated away from desktop OSs, where Android & iOS’s walls are holding them captive.


  • toastal@lemmy.mltoLinux@lemmy.mlIs Linux (dumb)user friendly yet?
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    25 days ago

    Huh. I still use proprietary software too—& I’ll make purchases for copyrighted music. But I have moved away from as much of it as I can when I had the opportunity or convenience to do so. Some proprietary software is basically irreplaceable & not built by megacorporations siphoning our private data. But things like chat apps? Music players? Code forges? There are tons of replacements…