nixGL VS nix

How can a program accomplish this? by using/doing something like virtualization? emulation? syscall/API translation? e.g. like WINE?

  [1] https://github.com/nix-community/nixGL

Essentially, running stuff that needs GL graphics is a bit funky... There's a workaround called nixGL though.

I think installing Calibre is a good use case for installing Nix (www.nixos.org).

Unfortunately, you might also need https://github.com/guibou/nixGL to run graphical apps under Nix. It's a shell script to use the correct OpenGL library.

Try the NixGL wrapper.

Are you running the Nix package manager on not-NixOS? If so I recall needing NixGL for OpenGL integration.

$ nix-channel --list home-manager https://github.com/nix-community/home-manager/archive/release-22.05.tar.gz nixgl https://github.com/guibou/nixGL/archive/main.tar.gz nixos https://nixos.org/channels/nixos-unstable

Needs a separate program to run GUI applications on non-NixOS systems

IMO the proper solution to this is Nix/Guix, since they have the best of both worlds (sharing libraries where possible, but allowing different versions where needed). Shame that libGL is a mess and as such is difficult to get right in this way, and as such you need hacks like https://github.com/guibou/nixGL for most GUI stuff. That said, people are working on improving the situation.

I get what you mean, but keep in mind that for every distro you're reliant on the community to get nvidia support integrated. Also if you only have few apps that require it, then the nixGL flake is not bad. https://github.com/guibou/nixGL

nix-channel --add https://github.com/guibou/nixGL/archive/main.tar.gz nixgl && nix-channel --update warning: unable to download 'https://cache.nixos.org/v5djb4jw3hg4brdbidqaspin8n8isyq6.narinfo': SSL peer certificate or SSH remote key was not OK (60); retrying in 259 ms these derivations will be built: /nix/store/gm6gq44ivdqgmrsvlsr08d2nqjircgds-nixgl.drv building '/nix/store/gm6gq44ivdqgmrsvlsr08d2nqjircgds-nixgl.drv'... while setting up the build environment: executing '/bin/bash': No such file or directory builder for '/nix/store/gm6gq44ivdqgmrsvlsr08d2nqjircgds-nixgl.drv' failed with exit code 1 error: build of '/nix/store/gm6gq44ivdqgmrsvlsr08d2nqjircgds-nixgl.drv' failed error: program '/usr/bin/nix-build' failed with exit code 100

> https://github.com/NixOS/nix/pull/9911#issuecomment-19252073...

As we covered in my last post, NixOS is a amazing Linux distribution for creating stable and declared environments. Now while this is amazing for a desktop setup, it is also perfect for a home-server or home-lab.

(Nix itself is slowly chugging along with Windows via MinGW - https://discourse.nixos.org/t/nix-on-windows/1113/108 and https://github.com/NixOS/nix/issues/1320 , for example.)

Nix is a cross-platform package manager. It uses the nix programming language. Nix and NixOs are often used in the same context, but while the first is a package manager, the latter is a linux distribution based on nix.

Today I want to talk to you about Nixos. What is it? Nixos is a declarative and reproducible OS, partly taking the words used on their own page. What does that mean?

Software developers often want to customize:

1. their home environments: for packages (some reach for brew on MacOS) and configurations (dotfiles, and some reach for stow).

2. their development shells: for build dependencies (compilers, SDKs, libraries), tools (LSP, linters, formatters, debuggers), and services (runtime, database). Some reach for devcontainers here.

3. or even their operating systems: for development, for CI, for deployment, or for personal use.

Nix provision all of the above in the same language, with Nixpkgs, NixOS, home-manager, and devShells such as https://devenv.sh/. What's more, Nix is (https://nixos.org/):

- reproducible: what works on your dev machine also works in CI in prod,

- declarative: you version control and review your configurations and infrastructure as code, at a reasonable level of abstraction,

- reliable: all changes are atomic with easy roll back.

Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.

- it reduces bloat, because you can generate an environment or OS image with only the software needed to run a specific program or service

My guess is that a big efficiency gain would come from the second point, because you don't waste CPU on code that you don't use.

Does this make sense? Has anyone explored this?

[0]: https://nixos.org

1) Setting up the development environment - I currently use devcontainers for most things, but may also dig into nix -> isolated, portable, repeatable development environment 2) Exploring Echo - understand routing, requests, response, etc. 3) Incorporate Templ - integration with Echo, template composition, etc. 4) Integrating TailwindCSS - config for use with Echo/Templ, development cycle, deployment, etc. 5) Add in HTMX - endpoints, template structure, concepts, etc. 6) hyperscript for interactivity - client side interactivity