ｔｏ⟁ｓｔ⟁ｌ
Fun Nix fact: there is no ”legacy Nix”. There is stable Nix & experimental Nix (the one using flakes whose API isn’t versioned or stable). You can call it “classic Nix” if you wish, but using the term “legacy” has the connotation that you think it does… & the experimental one is _not_ in a state to replace the stable option. Having been on the other side of this argument, a lot of really bad patterns emerge if you go flake-first instead of starting with what is stable & importing it into your `flake.nix` if you so choose to use it. #nix
Feb 2 at 10:41amWeb
Show threadembedding-shapesFeb 2

@toastal "legacy" is just code that was written before "you" cared about it.

Everything can be legacy if you're late to the party :)

Also, old unsupported versions are surely considered legacy even in your world?

Show threadｔｏ⟁ｓｔ⟁ｌFeb 2

@embedding_shapes Yeah, but it’s also needlessly agenda-pushing.

The funny one to me (even as an XMPP fan) is how in XEP-100 <https://xmpp.org/extensions/xep-0100.html> all non-XMPP protocols are considered legacy & the verbiage lives on despite XMPP’s wane in popularity (tho it does keep chugging + has had a bit of a uptick in usage more recently as modernization has come).

XEP-0100: Gateway Interaction

Show threadembedding-shapesFeb 2
@toastal I guess in that, the "legacy" they speak of is from their point of view, not the public's point of view of XMPP itself ;)