In practical perspectives, I'm mostly concerned about computer resources usage; I have computer resources constraints. So using Rust would benefit on that. But it is for a Web application backend. So, is it worth it having to learn Rust + Tokio + Axum, ... in this specific situation? Also, that this is mostly for initially prototyping an application. Also considering if I add developers in the future, they would most likely not be familiar with Rust, but with more popular frameworks such as Node.

[–] 3 points 2 years ago*

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...

  • source
  • parent
  • context
  • [–] 12 points 2 years ago* (7 children)

    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.

  • source
  • parent
  • context
  • [–] 3 points 2 years ago*

    GNU has interviews and more clarifying all the way back to MIT AI lab, lisp machines the printers proprietary code triggering free software movement, etc.

    Linux just happened because GNU hand't developed a proper kernel yet; Linus wrote that himself on an mail to the Linux Kernel or Minix mailing list IIRC.

  • source