I love seeing all these posts from NixOS newcomers! It seems anecdotally like LLMs have really given it a boost recently, I guess by reducing the intimidation factor of the language and the unfamiliarity? Of all the positive and negative outcomes I have imagined from LLMs, NixOS becoming popular was not one of them, but I'll take it.
> Development environments are still a pain. devenv.sh is great for web and backend
Weird, development environments are one of my favorite things about nix. I don't use anything like devenv.sh, just add a `flake.nix` to the repo defining a devShell, and then add `use flake` to `.envrc` and let direnv activate it. Every major and most minor editors have support for direnv, and if they don't, you can just launch them from a shell in that directory. This makes the only system dependencies for a great dev environment nix and direnv.
> I'm increasingly concerned with AUR-like trust issues
Once you've done it a few times, most things are pretty easy to package yourself, and you can just check those derivations into your git repo for your machines and use them. Especially if you're using LLMs, it shouldn't be all that hard to package what you need in most cases. For stuff that's more complicated or difficult, it's more likely there will be some kind of de facto standard flake for it.
I'm no AI booster by any stretch of the imagination, but it's not "run[ning] ... computer systems" in this case. Your NixOS setup is defined by declarative config files, and nix builds or updates a working system from them. AI in this case is just writing the config files, which you'd then (hopefully) read and at least vaguely understand before applying them.
I'm on year 6 and still feel the same way, using NixOS for all my machines, and also for my homelab servers (building on the main machine and then deploying over SSH). Everything else feels primitive by comparison. Rolling back is incredible.
I have one github repo with a top-level flake containing system definitions for all of my machines. Much of my config is modularized, so it's easy to take custom stuff from one machine and use it on another.
It's nice to hear that AI tooling is making it more accessible for people.
Yes, reading this I was thinking about how many of these problems go away with a nix environment. Certainly not all of them, but it’s a great way to get a reproducible build environment that includes direct specification of system dependencies.
I don’t know. I mean, I agree with you overall, but it seems like tons of engineers, especially here on HN, have been more than willing to go all-in on AI for at least the past year, with many dire warnings of “coding is a solved problem,” “if you’re not programming swarms of agents, you’re going to be left behind,” and so on.
This has not been my experience with my fellow engineers IRL on average, but I do feel like there is a significant contingent of us who are ready and raring to yield engineering in its entirety to the LLMs.
Los of innocent people are convicted of crimes they didn’t commit, often on the basis of their conversations with the police. You have every right not to fear it, but it is not an uncommon occurrence
Somebody else linked to a follow up talk by the lawyer in the video[0], in which he gives an example where this exact thing happened, and they wound up convicting the guy based on his attempts to help them. He was later exonerated.
Y’all are not good at reading comprehension, is the only label I’ll apply to you here. I’ve had good friends work for Meta, and I don’t judge them for it. I wouldn’t work there, because how I feel about the company means I can’t feel good about myself contributing to it in any significant way. Other people will feel differently, and, again, that’s fine.
But if you fundamentally disagree with a system, trying to avoid contributing to it in any way makes sense! Whether it’s making the algorithm or addictive more farming out moderation to underpaid contractors or building a cool open source library for frontend coding or whatever, you can choose not to do it.
Or you can say, my contribution is not meaningful enough to the broader organization for me to worry about my place in it. Or you can say, I will siphon money out of the beast and use it for good. You are still contributing to it, but how you feel about it is up to you.
My answer already addresses this? I didn’t say every engineer works on those things. I said it’s a spectrum, with the people working on those things at one end. I also already answered that they all contribute to the edifice, with different levels of moral culpability, which it’s up to them to hash out how they feel about.
Meta’s business is enabled by (practically) everyone who works for them, otherwise they wouldn’t pay them to work there. The storage compression algorithms are enabled by and contribute to the mission of the company.
If you’re comfortable knowing that your job is paid for by destroying society, and that your work makes that destruction a little more efficient, that’s fine. Storage algorithms are pretty low on the spectrum, and at least they may have some other uses if open sourced. For me, I wouldn’t do it, because I don’t want to contribute even in a small way to what Meta does. But others obviously can and do feel differently.
Obviously it’s a spectrum, no? Anyone contributing to the edifice is in some way furthering its core mission (giving girls depression, or utterly destroying society, depending on who you ask).
At one end of the spectrum you have very talented, smart engineers who could easily get a job anywhere, devoting their lives to targeting ads, surveillance, brain-hacking the masses with the algorithm in order to sell more ads, etc. At the other end is, let’s say, the cleaning staff. Meta would suffer if either group outright refused to work for them, but their mission is affected more by the engineers, they are harder to replace, they have many more options in terms of alternative employment, and they have greater knowledge of the impact of the business. Thus, they bear (much) higher relative moral responsibility. Compare to the cleaning staff, who, because of their relative lack of standing, agency (they likely work for some other company that Meta contracts with), or other options, bear negligible moral responsibility, even though their absence would likely make Meta’s offices uninhabitable.
Everyone working there is somewhere on that spectrum. They can make their own judgements about the degree to which they bear any moral culpability, but it’s not unfair to say that someone working on open source at Facebook still contributes to the overall mission by oss-washing facebook’s reputation, promulgating the brand into the engineering consciousness, etc., even if they are not directly contributing to giving girls depression.
I have rolled my own config now, but I started in spacemacs, and then moved to doom a while later. FWIW I found doom much easier to grok and generally stabler.
TBF to the parent, I also started in spacemacs, then doom, before rolling my own config some years ago, and my early experiences also felt like upgrades were really hard to deal with and often breaking.
I think most of that was because I didn’t understand emacs itself very well, and doom or whatever is an entire extra layer of code and idioms on top of that. Start adding in any custom packages you’ve installed and things get well outside of the realm where a beginner can comprehend them.
Like you, I also now have a pretty large number of packages, and rarely run into issues on update, with any issues that do occur being easy enough to fix. However, I think a lot of that comes from at this point having built my own emacs from the ground up, so I understand what all the components are doing, mostly…
I do think the community recognizes this to be an issue and is steadily working on improving beginner-friendly docs. I am about seven years into using Nix for various things, and can mostly solve most problems, but I won’t deny that the learning curve at the beginning was brutal. The real and most meaningful unlock is learning to read the nix language well enough to follow what is happening, then checking out nixpkgs locally to look at crate derivations and such to understand what idioms exist in “real code.” The module system also took ages to click for me, but was a big unlock.
Anyway, I hope the community continues to make the onboarding process more welcoming and easy. Personally, I am hopeful that guix will really take off at some point, because even though I get it now, I’d way rather read lisp than nix.
I resisted buying an apple tv for a long time, because I was going to have a playstation either way for games!
The (relatively) poor quality and difficulty of hooking my laptop up to the TV for criterion eventually pushed me to get one just for that, since there’s no word on if criterion has any plans to release an app for PS