she/her
Yeah I agree. Although recently I’ve become partial to toml… In the end I’ll use what’s common in the ecosystem I’m developing in
Nothing too major about how it’s usually used, but the yaml spec does allow arbitrary code execution when parsing a file and relies on the parser to have that feature disabled: https://en.m.wikipedia.org/wiki/YAML#Security
That’s why for python, yaml.save_load()
is a thing. That’s fine for your local config files and may even be a feature for you, but it shouldn’t be used to exchange information between services.
roleplay
If you do /* you don’t need that flag, as / will technically not get touched. Just everything in it
Give people the choice. Especially when sending graphics with small text, the loss of resolution is annoying
Is it really a spoiler if it’s halfway through chapter one? It’s like, the setup to the story
Doing the same for my S8
of course they’re not a drop-in replacement, as the cli is getting a major redesign, but as per your source
nix shell and nix develop are still experimental, so nix-shell is sticking around despite doing the same thing
it seems like they are made to fulfill the same purpose
Interesting, didn’t know the history of the command. But that post confirms my understanding, that nix shell/develop are the new replacements for nix-shell, with nix shell for temporary package installs and nix develop for debugging and developing
Source on the second statement? My understanding was that nix-shell is legacy for systems without flakes and nix-command enabled, and are being replaced by nix shell/run/develop
Careful, there’s three different terms in the mix here:
NixOS: an entire operating system, you don’t need this.
nix: the nix package manager. This is what you’ll need to install. look for single user install in the instructions.
home-manager: a module for nix. It’s aim is to allow declarative configuration of a users’ home configuration (and allow easier per-user install of packages on a global nix install).
If you want to go down the nix route, which I would recommend if you enjoy tinkering and having fine control over your system, you should start with installing nix. With that, you can already setup a shell that has the newest version of python available.
Going beyond that, I can link you some more resources, if you want c:
Forgejo is a free/open source code hosting site like GitHub or Gitlab. It’s a fork of Gitea, over concerns with management and commercialization. You might know it from Codeberg, which is one of the largest managed instances, but it’s really easy to host your own.
I’m still rocking my S8 active, and I’ll keep doing it until the battery dies or catches fire. Nothing they’ve added to phones in the last 7 years is worth it, imo
Only problem is that the storage is almost full from apps leaking data into locations not accessible from userland, so I’ll have to root it at some point. But I’m confident it got another 2-3 years in it
NixOS, probably some extreme bondage
Arch, masturbation
“good news honey, they heard your complaint and renamed it”
For reproducibility, nothing really beats NixOS. That’s not really what you’re asking for, as that would not involve Clonezilla.
If you’re frequently switching hardware, and want to have everything up and running, configured to your liking, in minutes, you’re gonna have fun with NixOS in the long term. But I’m not gonna sugarcoat it, it has a steep learning curve and does require you to enjoy some tinkering. Worth it, imo
Otherwise, just pick a distro that you enjoy and create a separate home partition, when it’s time to switch you do a fresh install and clone only the home partition. That’ll get you 90% of the way to have your old setup on the new device
I’m just gonna be patient. Vanilla Helix is very much usable for everything I need it for at the moment, with built in LSP support, and plug-in support is on the horizon. Not sure when exactly, but it’s gonna happen eventually
I’m halfway between hx and vim, I vastly prefer the helix/kakoune philosophy of selection, then action over vim, but I’m dearly missing plug-in support for Helix
Helix <3