• 4 Posts
  • 164 Comments
Joined 1 year ago
cake
Cake day: October 9th, 2023

help-circle












  • fl42v@lemmy.mltoMemes@lemmy.mlHowdy
    link
    fedilink
    arrow-up
    3
    arrow-down
    6
    ·
    20 days ago

    I kinda hope smth like that would happen. In such case Russia is likely to strike back, and having 2/3 nations with ambitions of world domination minding their own business for once may prove beneficial for the world in general. Can’t say Chinese government is a godsend with all their censorship, but at least I don’t really remember them baselessly attacking other countries as of recently




  • fl42v@lemmy.mltoNix / NixOS@programming.devThe future of software is Nix
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    2
    ·
    22 days ago

    Nix is typed: there are strings, paths, lists, attrsets, etc;

    Not sure what’s wrong with CLI, as I don’t really use it except nix flake update (although I remember updating stuff installed via nix profile being a bit cumbersome, but it’s not exactly a good practice to use it this way);

    Good point with cache, although stuff outside of nixpkgs sometimes provides their own caches which are trivial to enable;

    Nobody forces you to use github:nixos/nixpkgs, it’s just a regular input. Ppl quite often have their own forks. It’s also trivial to use stuff from outside nixpkgs (also just another input);

    There are different builders (e.g. buildGoModule);

    Idk where you’ve found toxic community, my interactions have been pretty nice so far (mostly matrix rooms);

    GUI is optional, just like for all the other package managers. And it exists: https://github.com/snowfallorg/nix-software-center

    Perfectly agreed with nix not (yet 🙃) being the best thing that exists, tho, albeit due to different reasons. For example, it’s a PITA to debug, and the error messages are sometimes unhelpful.



  • I’m not sure you can classify this as a failure, as explicitly prohibiting interfacing with non-agpl stuff would greatly limit the amount of stuff you can license under it, perhaps up to the point of making it generally unusable. As for “not like that”… Well, yeah. But you can’t deny it’s misleading, right? Free software kinda implies you can modify it whatever you want, and if it’s a free ui relying on a source-available middleware… Turns out, not so much.

    Although, a posdible solution would be require explicitly mentioning if you’re basically a front-end for something; but I’m not sure if it can be legally distinguished from the rest of use-cases.