Plutus, Haskell, Nix, Purescript, Swift/Kotlin. laser-focused on FP: formality, purity, and totality; repulsed by pragmatic, unsafe, “move fast and break things” approaches


AC24 1DE5 AE92 3B37 E584 02BA AAF9 795E 393B 4DA0

  • 0 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle

    1. Mlem: missing a lot of features but the ones that they have work very well. This one feels the most native because it is. This is my current choice because it is actually native and open source. That icon is ugly as hell, though.

    2. Voyager: this one is a month ahead on features of ALL other lemmy apps. this one is the most feature-rich in that they have the ability to edit posts and do all kinds of other stuff. The non-native web app aspect causes it to lose LOTS of points in my book

    3. Memmy: this one was easily my favorite but the recent updates have started to show how poorly architected it is. They have a TON of work to do under the hood to make this one feel solid again…and honestly, I sincerely think it may never feel as responsive and snappy because they made the strange decision to make an iOS only app in react native…

    4. Liftoff: this one is pretty good but it just goes too far from the standard that Apollo set that I feel awkward in it.

    5. Bean: this one is early days but already has some cool stuff that I wish other apps had (the profile button at the bottom has the icon from the currently signed-in user) I had been asking for that feature from other devs for FAR too long.








  • demesisx@lemmy.worldtoProgrammer Humor@lemmy.mlworks on my machine
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    I know it’s a strange place for this conversation but the facts remain: docker images don’t do this and nix flakes actually do. As the video I linked demonstrates and you allude to, Docker files aren’t 100% hermetic (which means they’re not reproducible) while Nix flakes actually do achieve this. Watch the video I linked for more explanation which directly talks about how nix works with the goals of Docker that you mentioned in the head of your last comment. I hope my non-confrontational tone comes across somehow. This is all said with respect and in the spirit of science.


  • demesisx@lemmy.worldtoProgrammer Humor@lemmy.mlworks on my machine
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    1 year ago

    No offense but it sounds like you don’t actually understand nix flakes if you think they’re 1:1 equivalent to Docker.

    They simply are not containers. They allow the declarative BUILD of any derivation at any time in the future. They hermetically lock all dependencies and build instructions which allows you to archive and reproduce the EXACT content-addressed dependency graph of the software. You can rebuild using a flake while Docker doesn’t actually allow that same hermetic reproducible guarantee whatsoever.

    See here for a much better explanation of the glaring differences between the two: https://youtu.be/0uixRE8xlbY

    You could even build a container with a flake though I’d recommend OCI instead because they’re an open standard…