Models could be run offline and/or free, e.g. gpt4all, starhugger for emacs, huggingchat... Also, this is a fast-pace changing industry, we can only try and adapt using such tools at our disposal. You might use a tool or service that uses AI and don't even notice it.
Hahahah actually this in conjunction with Lex's talks/interviews is probably what got me thinking more about all this. Masterpiece anyway
Maybe they will pay a little fine---and you won't be getting the money either---while their profits skyrocket. It's always like this, so I don't even bother.
I also think this is the way. Glad to know I am not alone. Thank you!
PS: I have a pretty nice and modularized GNU Emacs config, but it's to me just as Lex we are missing a ton by constraining only on GNU Emacs.
Guess I'll be using GNU Emacs, VSCode, Helix, Eclipse hsha
I'm actually sad since acnkowledging that as I invested too much in GNU Emacs
Just do it like me and listen to nature sounds like gentle rain.
Not really... Many are just devs used to say Windows who happened to get to work in a linux environment.
Nix files are Nix [function] expressions to declare and set your system; there are many options you can set for example. You just need to learn a few chapters of https://nixcloud.io/tour/ and https://nixos.org/manual/nix/stable/language/, also modularization using imports.
For user/de configuration, you can either do the usual way or use home-manager.
Basically all that. The unfinished part IMO is mostly for use in developer use cases, and that some ecosystems like JVM are not as well supported.
Can run yes, given that you have to spend some time learning Nix and NixOS specifics. I do that myself.
You either package the software if it is easy to do so—take a look a at nix-init which eases the process—or use Flatpack, containers, steam-run...
It all began with Nix software build system and package manager; they needee a way to build, compile software in a reproducible way. That is, if it builds on my machine, it should build on yours too given some constraints. Then they build a whole package repository for such sofware or package definitions, Nixpkgs, that can be build or retrieved using Nix package manager. Nixpkgs grew to be a repository for enabling runnig an GNU Linux OS on it: NixOS. It is declarative in the sense you write what it should contain like packages and behaves like system services. For example, see https://git.sr.ht/~misterio/nix-config.
Atomic in the sense that when you want to change system's configuration or state, everything should suceed in that update, otherwise fails; it is everything or nothing. This enables storing previous and current system revisions, so can rollback to previous state.
Nix plus things like flakes, nix shell, enables a build inviroment akin to containers, but much better, correct, and flexible.
Haskell is just an ecossytem Nixpkgs support.
I quoted your comment in the original post if you're ok this, thanks for your comment