![Avatar](/_next/image?url=%2Flemmy-icon-96x96.webp&w=3840&q=75)
dukk
Thank god for NixOS. (My daily on my laptop, seriously flakes + nix-direnv
is godsend for productivity. Reliable development environments and I don’t have to lift a finger!)
I just jumped in headfirst. I love it. It’s really just Nix, but with options to configure your whole system to your liking.
Stability’s been rock-solid and I haven’t yet encountered anything truly headache-inducing.
Here’s some starter advice:
- Try to start with flakes. Nix channels are known for being…unreliable at times.
- Start small, slowly extend. Many people’s Nix configs are often insanely abstracted and modularized. Personally, I started my flake config by installing KDE + Nix, and then linking the
configuration.nix
to the flake. (Remember, flakes just package the config, they’re not responsible for configuring the system).
My Nix config is relatively basic (check it out here, so feel free to look around trying to understand it. I’d also suggest using Home Manger if you aren’t already.
The NixOS forums are great for getting help. I’ll also point you towards the Catppuccin Discord server, the NixOS thread there is filled with many helpful people who helped me get started. (If you decide to swallow the Nix pill, feel free to join and ping me(my username’s Dukk); I’ll add you to the Nix thread).
I mean, technically, Option
s are monads, so…
I think all of these can be recompiled at runtime.
Askama seems to be a popular and mature option here. Yew is also pretty popular here, uses a VDOM and provides a powerful front end (great for SPAs) I’m most likely going to go with tide-jsx, it’s like HTML but it supports Rust expressions thru a macro, which is exactly what I need. Liquid is also pretty secure, so that’s an option.
Askama and Yew are pretty mature, so they probably have reasonable security. I would check their docs, however.