kreetx

28 ms·

541.
by kreetx 3y ago
Much of JavaScript's underlying machinery is also written in C++, how do you feel about that?
542.
by kreetx 3y ago
Yeah. I guess the answer is that there weren't (m)any configuration languages which had functions - even YAML itself (which doesn't have functions) came out a few years before nix. Cue, starlark, dhall are all much later.
543.
by kreetx 3y ago
What I meant to say is that if when somebody both admits their misunderstanding , admits it, then starts a discussion on what to do about it, then I don't understand the "this guy is a joke" part. Don't you wish everyone
544.
by kreetx 3y ago
This is a github issue to discuss this topic, not a breaking change.
545.
by kreetx 3y ago
Do the visits to Home Depot also benefit from using a gasoline car somehow, i.e is it far away or there haven't been many electric trucks until recently?
546.
by kreetx 3y ago
Forgot "We only do road trips"?
547.
by kreetx 3y ago
The argument sounds similar to "if you have this big chunk of code already written, it's really easy to change this one thing".
548.
by kreetx 3y ago
With nix, you wouldn't need to back up the images - you can start from source every time.
549.
by kreetx 3y ago
Reproducible build means that you get your source code from somewhere, it has dependencies listed, you install those, then you compile your artifact from your source , and the resulting binary or container is always the same. You can delet
550.
RFC 1607 by Vint Cerf: A View From the 21st Century (April 1, 1994)(datatracker.ietf.org)
1 points by kreetx 3y ago|0 comments
551.
by kreetx 3y ago
How do you do reproducible builds at the moment?
552.
by kreetx 3y ago
Here is the discussion https://github.com/NixOS/nixpkgs/issues/300055
553.
by kreetx 3y ago
If you already knew docker doesn't give reproducibility you should have just said so from the get go. ;)
554.
by kreetx 3y ago
But if you read those links, you'll see that it's not quite there yet. Docker in general can't solve reproducibility - it's the package manager within any container that does that.
555.
by kreetx 3y ago
I'm sorry to hear that you've had a bad experience with it, it does take a while to get used to. I guess there is still much UX work to be done there.
556.
by kreetx 3y ago
You get the same hash only if you build the image when none of your dependencies were updated in the mean time. If you `apt-get install something` in a month, the resulting image will most likely not have the same hash. Docker itself doesn&
557.
by kreetx 3y ago
Docker gives you the headache of not actually giving you reproducibility. If you haven't been bitten by it then I don't think you have tried. For popularity, I wouldn't actually mind if nix weren't all that popular, but
558.
by kreetx 3y ago
Yes, but every other thing you install in the container you'd somehow need to manage the hashes for, too.
559.
by kreetx 3y ago
What if the environment needs more packages installed via apt, do you save those hashes somewhere, too?
560.
by kreetx 3y ago
Well, nix gives you that too, plus determinism.
561.
by kreetx 3y ago
I mean hashes of what , not which hash algorithm . If you build the same Dockerfile, then I don't think you'll get the same hash, so I'm not sure what the use of that hash would be. (Did you mesn a hash of some other thing?
562.
by kreetx 3y ago
What hashes do you use in docker or vagrant?
563.
by kreetx 3y ago
Right, but isn't the feature you want in a disposable environment is that it builds? Determinism guarantees that, but isolation doesn't.
564.
by kreetx 3y ago
I think it's you who is missing the point: the learning environment won't build as neither docker nor vagrant will give you reproducible environments, while nix will. Sure, you can make your nix environments dynamic too, but havin
565.
by kreetx 3y ago
> In docker and vagrant you do it the same way, the hash of the specific artefact. No, in nix you pin the commit hash of nixpkgs, which gives you the exact same package set every time. But with a Docerfile, even if you add it to your pro
566.
by kreetx 3y ago
In nix you can pin your environment down to a commit in nixpkgs, from which whenever you build your system (i.e, artefact), the result will be the same. How do you achieve this in docker or vagrant? > Usually you don't really want &
567.
by kreetx 3y ago
I'd say nix is the more deterministic way to get all, and only, the things you absolutely need . Docker has the same issue as vagrant that you'll get a different debian depending on the day you init the VM, run apt, and so on.
568.
by kreetx 3y ago
Someone should do an experience report on adding the same storage system to both databases. What you say looks powerful but Facebook added their MyRocks to MySQL.
569.
by kreetx 3y ago
Not an expert, but briefly looking into this, MySQL is 1. easier to configure and manage 2. faster for read-heavy workloads 3. has pluggable storage engine (though, if you care about this, then 1. likely doesn't matter anymore)
570.
by kreetx 3y ago
I'm an software developer so I would have generally looked at the same area of roles. What specifically happened though was that as I didn't pull it off with my SaaS idea during the time I had planned, so after about ~10 months I

More ›