121–130 of 201 posts
I tried devbox and some other tool in that field. I then tried dev containers. Dev containers won. Hands down.
They're nice, but they lock you into vscode
I tried devbox and some other tool in that field. I then tried dev containers. Dev containers won. Hands down.
You don't need to choose :). You can use Devcontainers with most of the Nix tools, including Devbox. See https://containers.dev/supporting
You are right, but at the end of the day, I prefer to write my own installation scripts or "features" than dealing with Nix.
Maybe some day I'll go back to a nix tool to help writing a complex devcontainer.json with everything I need.
Has the situation improved?
Earlier quoted context omitted.
You don't need to choose :). You can use Devcontainers with most of the Nix tools, including Devbox. See https://containers.dev/supporting
I just gave that link to someone else who commented here. :) You are right, but at the end of the day, I prefer to write my own installation scripts or "features" than dealing with Nix. Maybe some day I'll go back to a nix tool to help writing a complex devcontainer.json with everything I need.
"But there are hoards more that think you should just write hacky shell scripts and bugs don't really matter anyway."
Earlier quoted context omitted.
I just gave that link to someone else who commented here. :) You are right, but at the end of the day, I prefer to write my own installation scripts or "features" than dealing with Nix. Maybe some day I'll go back to a nix tool to help writing a complex devcontainer.json with everything I need.
https://news.ycombinator.com/item?id=39697259 "But there are hoards more that think you should just write hacky shell scripts and bugs don't really matter anyway."
Yeah, I am aware writing my own scripts isn't ideal, but this is the current state of affair.
I could use mise to install most tools though. I would need to figure out what the overhead would be.
One question: does Flox need Nix preinstalled? I don't see any mention of Nix in the installation guide. If Fkox doesn't need Nix install it would be a huge game changer.
How does nix deal with different CPU architectures? If I have some developers using an ARM based macbook, and some devs on an x86_64 based machine, is it easy to support both without much maintenance?
But in practice it's really easy. Though if you're all into robustness you should probably test on the same arch you deploy to eventually.
Earlier quoted context omitted.
So what you are offering here is essentially a small UX improvement over sharing a flake with a devshell in a Git repo? I'm the first to admit that nix is way too cumbersome to use, but this alone doesn't seem like enough value add.
If you think this is a "small" improvement on Nix's UX you clearly have never used Nix.
Last I tried to use Nix there was lots of confusion over flakes - some tutorials suggested using them and others saying they are still in development. Has the situation improved?
I think the flakes problem come from two things:
- flakes are labelled experimental for years now (I think it might be almost 5 years now) which creates confusion with new users, but they are universally used nearly everywhere now - there seems to be some bad blood[1] between https://determinate.systems/ company and the long time Nix users and developers who are accusing them that they are using Nix for their benefit with not contributing back. From my understanding Determinate Systems introduced flakes and probably this why there's some resistance to it by some.
But to answer your question, pretty much everyone adopted flakes and guides that don't use them are most likely old.
[1] https://discourse.nixos.org/t/introducing-flakehub/32044