nixpkgs-mozilla VS rust

Do I know how to do this? No, but this real-world and the wiki might be places to start. I'll eventually have to figure this out myself so if I get around to that I'll post what I learn too

Is there a way to still keep it pure? From the nixpkgs-mozilla repo:

Fenix provides the minimal, default, and complete profile of rust toolchains, latest profile of nightly toolchains, nightly version of rust analyzer and its vscode extension. It aims to be a replacement for rustup and the rust overlay provided by nixpkgs-mozilla.

Firefox-nightly is maintained in the official nixpkgs-mozilla repo, so you're incorrect on that point. It's unreasonable to ask me to pick out examples for you, just to prove that numbers have actual meaning. However, feel free to peruse recently added packages and see which ones do and don't make their way to the AUR.

4. I would suggest Mozilla's Rust overlay or fenix or similar instead of Rustup - that would be more of the "Nix-way" to acquire the toolchain and you can still manage multiple versions. Not sure what the Ruby equivalent is, I don't do Ruby.

and for building software, I'd suggest using flakes for both the software repo and the system configuration, because then you can just add the software flake as an input to the configuration flake and that's it, and you have the build code separated from your system. Using e.g. "ssh+git://git.example.com/secret-project" as the input should work, though I don't know which user's SSH keys it will try to use. I think mozilla-overlay is a good example, the flake outputs are a couple overlays you can add to your system's nixpkgs (here's how to add overlays in nixos), especially take a look at phlay-overlay in the mozilla repo, it's an overlay that adds one package so it's pretty simple. You can do something similar without using flakes though, fetching the sources needs to be done differently though, I know there's the builtins.fetchGit and builtins.fetchTarball functions, the former I assume would work similarly with SSH keys, no idea about the latter. The rest, making a derivation for building the software and adding it to your configuration's nixpkgs, should work the same.

I am on NixOS at the moment, Widevine (Nightly) on Arch was working well. I installed Nightly from https://github.com/mozilla/nixpkgs-mozilla.

Fenix provides the minimal, default, and complete profile of rust toolchains, latest profile of nightly toolchains, nightly version of rust analyzer and its vscode extension. It aims to be a replacement for rustup and the rust overlay provided by nixpkgs-mozilla.

> There are online Rust compilers and interpreters already if you just want to rapid prototype and develop ideas in Rust

You are responding to one of the key developers of Rust early on[1], who's been working with the language for 14 years at that point.

[1] https://github.com/rust-lang/rust/graphs/contributors?from=2... and he's still #16 in commits overall today, despite almost no activity on the rust compiler since 2014.

If you haven't dipped your touch-typing fingers into Rust yet, you really owe it to yourself. Rust is a modern programming language with features that make it suitable not only for systems programming -- its original purpose, but just about any other environment, too; there are frameworks that let your build web services, web applications including user interfaces, software for embedded devices, machine learning solutions, and of course, command-line tools. Since a custom GitHub Action is essentially a command-line tool that interacts with the system through files and environment variables, Rust is perfectly suited for that as well.

Here's an example of someone citing a disagreement between CRT and shell32:

https://github.com/rust-lang/rust/issues/44650

This in addition to the Rust CVE mentioned elsewhere in the thread which was rooted in this issue:

https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html

Here are some quick programs to test contrasting approaches. I don't have examples of inputs where they parse differently on hand right now, but I know they exist. This was also a problem that was frequently discussed internally when I worked at MSFT.

    #include 

> instead of choosing a certain numbered version of the random library (if I remember correctly) I let cargo download the latest version which had a completely different API.

Yeah, they didn't follow the instructions and got burned. I still think that multiple things went wrong simultaneously for that experience. I wonder if more prevalent uses of `#[doc(alias = "name")]` being leveraged by https://github.com/rust-lang/rust/pull/120730 (which now that I check only accounts for methods and not functions, I should get on that!) so that when changing APIs around people at least get a slightly better experience.

Almost fixed the compiler: https://github.com/rust-lang/rust/pull/123325

Rust: A secure, efficient, and modern programming language (omitting ten thousand words). You can simply follow the installation instructions provided on the official website.

Recently did something similar in Rust but for generating SVGs. We've adopted it for snapshot testing of cargo and rustc's output. Don't have a good PR handy for showing Github's rendering of changes in the SVG (text, side-by-side, swiping) but https://github.com/rust-lang/rust/pull/121877/files has newly added SVGs.

To see what is supported, see the screenshot in the docs: https://docs.rs/anstyle-svg/latest/anstyle_svg/

We strongly believe in Rust as a powerful language for building production-grade software, especially for systems like ours that run alongside Kubernetes.