ris

25 ms·

241.
by ris 5y ago
> For home desktop use I don't really see the point Lucky that you don't need to run NixOS as your OS to get a lot of the advantages from it then. I use debian for my boring desktop applications but have Nix available to me for
242.
by ris 5y ago
> I've been looking for a simple package management solution that doesn't interfere with my OS and simply puts all packages in /some_location/package/version, and that allows me to install packages on remote mach
243.
by ris 5y ago
You should categorically not be implementing chaining semantics unless your operations are non-mutating. If they are mutating and you return the same object, it's possible for people to go years without realizing that's what&#x2
244.
by ris 5y ago
Or just use Nix and alter or override the package definition to your needs. Or if you really want to build it interactively $ nix-shell '<nixpkgs>' -A somepackage and run `unpackPhase`, `patchPhase`, `configurePhase
245.
by ris 5y ago
That class of attacks exists anyway unless you're using trusted boot. After all, your MBR isn't encrypted is it?
246.
by ris 5y ago
But the same is also true for rotating the bracelet isn't it?
247.
by ris 5y ago
> But the thing about Nix is that it just adds even more complexity It absolutely doesn't. I'm someone who is fairly fluent with Nix, and in comparison the complexities of running a non-trivial docker-compose setup gives me nig
248.
by ris 5y ago
But you could surely just randomly vary the beamforming to get the same effect, right?
249.
by ris 5y ago
Oh, I use Nix because it does provide less complication in my life. It's just necessary to wrap your head around a few core principles first, which can be a little mind-bending when you start out (no fixed /usr locations? huh?)
250.
by ris 5y ago
A few packages are effectively rolling even in the stable distribution, because they have a high volume of security fixes and it's a high-impact application. We just don't have the resources to backport all the fixes. This isn&#
251.
by ris 5y ago
https://github.com/NixOS/nixpkgs/issues/131486 leave a thumbs-up on the packaging request if you care about it.
252.
by ris 5y ago
What I'm hearing is "I really don't like the way traditional systems are designed and I don't want to have to learn anything new!" Nix is different, unapologetically so, that's the issue. And if it had to be
253.
by ris 5y ago
Are they not able to just use phase shifts and beamforming on the transducer array instead of the odd keep-moving-your-bracelet design?
254.
by ris 5y ago
You don't expect to have to check for "silent mode" as a "feature" on a checklist. It generally tends to be a bit of a given. I also have one of their newer feature phones and still find it woefully anaemic compar
255.
by ris 5y ago
I fell for it with the "new" 3310, only to find the phone was so underfeatured it didn't even have a "silent mode" feature. These new nokias are a pale imitation of their namesakes.
256.
by ris 5y ago
The Open Source Ecology designs have always struck me as a great way of losing a limb.
257.
by ris 5y ago
These are the nasty solutions I have to deal with at work all the time and my entire job consists of handling things when the "quick" bash cloud init script that someone wrote and various people have made additions to over the yea
258.
by ris 5y ago
> I'm a SWE and I don't grok it yet. I think the biggest difficulty most people have is that it's a pure functional language, and that is quite foreign to a lot of people, even many SWEs. It's something that's no
259.
by ris 5y ago
If you're interested in this article watch his episode on TinTin.
260.
by ris 5y ago
I think one of the reasons it feels like this is with Nix, the guts of what people are setting up are all exposed, right there in robust code. You see what's going in to the sausage. In comparison, I've worked in projects which di
261.
by ris 5y ago
> « docker build » already exists and can already be made deterministic Truly deterministic Dockerfiles are a rare thing to find among the ecosystem. And we haven't even got into docker's poor support for unprivileged container
262.
by ris 5y ago
> If that were true f.lux wouldn't be so significant in my experience. Let me introduce you to something called the placebo effect..
263.
by ris 5y ago
I'm not sure what would actually happen in reality, whether a single CVE would get endless addenda listing the packages affected by an upstream vulnerability. I certainly see plenty of new CVEs go past which are of the form "xyz h
264.
by ris 5y ago
(I'm merely a lowly maintainer in NixOS, shoulders of giants etc.)
265.
by ris 5y ago
And if the upstream developers are unresponsive, or only provide the bump with the latest bleeding-edge version which you can't upgrade to yet?
266.
by ris 5y ago
Just imagining the joy of broken firmware updates being pushed out to all my lightbulbs...
267.
by ris 5y ago
Well, it's what traditional distributions do every day. In NixOS, we try to work the test suites into the build process and rebuilds happen when any dependencies change, so I'd like to think we get (almost) the best of both worlds
268.
by ris 5y ago
Someone's a subscriber to breadsword's youtube channel.
269.
by ris 5y ago
I eagerly await some concrete implementations of these new ideas. In the meantime I'm waiting for the first big vulnerability in a widely used golang or rust library to see if downstream projects pinning it also release CVEs as the
270.
by ris 5y ago
I do sympathize as I spend a lot of my time maintaining distro packages. But I also fear that in this new world of golang and rust projects with statically linked libraries, few people take their reporting responsibilities seriously. Hell,

More ›