Just a basic programmer living in California
Nix / NixOS @programming.dev Experiments configuring jj fix with Nix devShell
Nix / NixOS @programming.dev Embedded SQL highlighting in Neovim, a look into Treesitter, and some NixOS patching
Programming @programming.dev The 6 Big Ideas of Typescript
Nix / NixOS @programming.dev run Kodi media center
Linux @programming.dev Selective VPN confinement in NixOS
Nix / NixOS @programming.dev Selective VPN confinement in NixOS
Nix / NixOS @programming.dev Patch interpreter path in embedded binary?
Nix / NixOS @programming.dev work around a misbehaving binary cache
Nix / NixOS @programming.dev Native Wayland gaming with Wine on NixOS
Rust @programming.dev Comprehending Proc Macros
Rust @programming.dev “Truly Hygienic” Let Statements in Rust
Nix / NixOS @programming.dev gnome-keyring as ssh agent in lightweight window manager
I agree that this doesn't seem necessary. Personally I think Nix would be a good candidate for dependency management that works consistently between languages. I think that may be partway set up for Haskell, and I've noticed that nixpkgs has a good collection of Python dependencies. But for most cases the Nix flow currently usually involves using the language's bespoke dependency manifest to generate a Nix expression that downloads dependencies from the language's bespoke package repo.
One advantage of Nix is that you don't need all packages in one repo. Nixpkgs is mostly geared for the NixOS Linux distro. Each language ecosystem could have its own repo if that makes the most sense, with Nix being the common connective language.