51–60 of 71 posts
Earlier quoted context omitted.
This must be a different "just" from the just I'm used to! Weeks sounds way more accurate than 1-2 hours.
this looks like weeks to you? { pkgs, ...}: { home.packages = with pkgs; [ neovim lazygit ]; }
Earlier quoted context omitted.
Ah yeah I wouldn't count that as being a small learning curve because you haven't actually learnt anything. Valid approach though I guess.
I'd disagree. You're not learning anything if you close your eyes and tell your LLM "set up home manager" - but you'll learn a lot if you read the code it produces, ask clarifying questions, and actually try to understand what is happening. It's just a tool that helps you avoid doing tons of research manually by searching google, and helps you avoid dealing with ugly nix syntax.
Therefore my middle ground is devbox.
It is like python vietualenv but backed by Nix. So I have a devbox.json file to define packages and devbox will do the Nix part for me.
I am getting a MacOS and Linux setup from this for aarch64 and x86
Earlier quoted context omitted.
This must be a different "just" from the just I'm used to! Weeks sounds way more accurate than 1-2 hours.
this looks like weeks to you? { pkgs, ...}: { home.packages = with pkgs; [ neovim lazygit ]; }
I think you are re-inventing the wheel https://github.com/nix-community/home-manager
Earlier quoted context omitted.
I use mise, but its conclusion that everybody needs to write an aqua plugin now is annoying. They need to make plugin-making a lot easier.
What conclusion do you mean? Aqua is just one of the many backends it supports. For example there's also the GitHub backend which lets you install binaries from releases, no plugin needed at all.
Overall there's too many ways to install things and it's not easy to add any of them. Asdf plugins were easy, but insecure (which could be fixed, but whatever). Everything else requires more research because it's more technical.
If you want this makefile way, use Justfiles,which are modernized Makefiles so you dont have 30 years of cruft and such being injected into it.
But also at the end of the day, Mise exists and is directly targetted for this.
I personally use Brew bundle files + Dotter for my home/tools management. Brew bundles also support Flatpaks these days and i can install those too.
You can literally use Brew for a lot of things. Linux brew is pretty good these days. If you want this makefile way, use Justfiles,which are modernized Makefiles so you dont have 30 years of cruft and such being injected into it. But also at the end of the day, Mise exists and is directly targetted for this. I personally use Brew bundle files + Dotter for my home/tools management. Brew bundles also support Flatpaks t…
What's the use case for homebrew on Linux these days? Most distributions have their own package manager, which you almost always end up using anyways, so already you're adding an extra package manager. Besides that, most of the community isn't using homebrew, so clearly won't have "more" packages, and the packages it'll have will be less reviewed than the ones in your distribution. I can't really see any point to use homebrew on Linux except "I used to use it on macOS", which doesn't feel that strong of a use case really.
You can literally use Brew for a lot of things. Linux brew is pretty good these days. If you want this makefile way, use Justfiles,which are modernized Makefiles so you dont have 30 years of cruft and such being injected into it. But also at the end of the day, Mise exists and is directly targetted for this. I personally use Brew bundle files + Dotter for my home/tools management. Brew bundles also support Flatpaks t…
> Linux brew is pretty good these days. What's the use case for homebrew on Linux these days? Most distributions have their own package manager, which you almost always end up using anyways, so already you're adding an extra package manager. Besides that, most of the community isn't using homebrew, so clearly won't have "more" packages, and the packages it'll have will be less reviewed than the ones in your distribut…
Sooo, i dont have a system package manager to use to add more packages, not without building my own image ontop of Bluefin/Bazzite.
Also, all the packages on Brew are fairly well tested, while mostly on OSX, they officially release Linux prebuilts for Linux and get tested equally. Brew has been around for ages.
And I havent used MacOS for 8-9 years, and only for a small stint. Not long enough for it to do things.
Also per official stats: https://formulae.brew.sh/analytics/os-version/90d/ Ubuntu makes up ~20% of brew usage, and the Universal Blue family is about 2% and growing.
There is absolutely a usecase for it and its just as good if not better, as most tools are more likely to be statically built, and you donthave a giant dependency mess and other nonsense to deal with. Its cleaner.
On an immutable distro, its a lot of Flatpak, AppImage, and Brew/Mise/etc. Layering packages is greatly discouraged and as the ecosystem moves towards Bootc images over OSTREE ones, the option will go away entirely. You either build a custom image with yoru custom stuff layered on yourself (there are templates and Github CI stuff to help with it.) or you use other package managers.
Also another win is weith Brew, i can reproduced my tools and environment quickly and dont have to deal with Distro quirks. Brew works the same on almost every distro, same pathings, same behavior, and even offers the Brewfiles to let me specify my setup.
I recently switched jobs and had my work setup installed and created within mins of booting into a fresh install and I was working shortly after.
you can declare tools and tasks with http://mise.jdx.dev/