uthredii
@uthredii@programming.dev
- Submitted 8 months ago to programming@programming.dev | 1 comment
- Submitted 9 months ago to unitedkingdom@feddit.uk | 1 comment
- Comment on Does Immigration Make House Prices Go Up? 11 months ago:
The video isn’t about that at all. I really wish people (not just you) would watch it before commenting or voting.
- Submitted 11 months ago to unitedkingdom@feddit.uk | 8 comments
- Comment on Discourse, the free forum platform, is now joining the Fediverse. 11 months ago:
Discourse and Lemmy are both based around topics/communities so hopefully there will be better federation here. E.g. being able to follow a discourse topic from lemmy would be really cool.
Hopefully they have done this in a way where Lemmy can federate with then easily.
- Comment on Discourse, the free forum platform, is now joining the Fediverse. 11 months ago:
We can already view mastodon threads that are linear inside Lemmy.
- Comment on To catch a catfish 11 months ago:
Oh, sorry. It wasn’t for me earlier (I linked through from Firefox suggestions)
- Submitted 11 months ago to technology@lemmy.world | 7 comments
- Submitted 11 months ago to unitedkingdom@feddit.uk | 1 comment
- Submitted 1 year ago to programming@programming.dev | 3 comments
- Submitted 1 year ago to unitedkingdom@feddit.uk | 3 comments
- Submitted 1 year ago to programming@programming.dev | 9 comments
- Comment on Effortless dev environments with Nix and direnv · Determinate Systems 1 year ago:
Nice, I hadn’t heard of that before, will check it out!
- Comment on Ditching Docker for Local Development 1 year ago:
I just see it as less practical than maintaining a toolchain for devs to use.
There are definately some things preventing Nix adoption. What are the reasons you see it as less practical than the alternatives?
What are alternative ways of maintaining a toolchain that achieves the same thing?
- Comment on Google's trying to DRM the internet, and we have to make sure they fail 1 year ago:
I think it depends on the website. There are some websites where chrome will work better either because chrome works better with certain libraries/technologies or because the developers put more time into optimizing for chrome.
On the other hand firefox might have less bloat around telemetry that gives it an advantage too.
- Comment on Ditching Docker for Local Development 1 year ago:
That seems like an argument for maintaining a frozen repo of packages, not against containers.
I am not arguing against containers, I am arguing that nix is more reproducible. Containers can be used with nix and are useful in other ways.
an argument for maintaining a frozen repo of packages
This is essentially what nix does. In addition it verifies that the packages are identical to the packages specified in your flake.nix file.
You can only have a truly fully-reproducible build environment if you setup your toolchain to keep copies of every piece of external software so that you can do hermetic builds.
Nix verifies the external software is the same with checksums. It also does hermetic builds.
- Submitted 1 year ago to programming@programming.dev | 5 comments
- Submitted 1 year ago to privacyguides@lemmy.one | 93 comments
- Comment on Ditching Docker for Local Development 1 year ago:
Related, this article talks about combining nix and direnv: determinate.systems/posts/nix-direnv
Using these tools you are able to load a reproducible environment (defined in a nix flake) by simply cding into a directory.
- Comment on Ditching Docker for Local Development 1 year ago:
Are you saying that nix will cache all the dependencies within itself/its “container,” or whatever its container replacement would be called?
Yep, sort of.
It saves each version of your dependencies to the /nix/store folder with a checksum prefixing the program name. For example you might have the following Firefox programs
/nix/store/l7ih0zcw2csi880kfcq37lnl295r44pj-firefox-100.0.2 /nix/store/cm1bdi4hp8g8ic5jxqjhzmm7gl3a6c46-firefox-108.0.1 /nix/store/rfr0n62z21ymi0ljj04qw2d7fgy2ckrq-firefox-114.0.1
Because of this you can largely avoid dependency conflicts. For example a program A could depend on
/nix/store/cm1bdi4hp8g8ic5jxqjhzmm7gl3a6c46-firefox-108.0.1and a program B could depend on/nix/store/rfr0n62z21ymi0ljj04qw2d7fgy2ckrq-firefox-114.0.1and both programs would work as both have dependencies satisfied. AFAIK using other build systems you would have to break program A or program B (or find versions of program A and program B where both dependencies are satisfied). - Comment on Ditching Docker for Local Development 1 year ago:
You might be interested in this article that compares nix and docker. It explains why docker builds are not considered reproducible:
For example, a Dockerfile will run something like apt-get-update as one of the first steps. Resources are accessible over the network at build time, and these resources can change between docker build commands. There is no notion of immutability when it comes to source.
and why nix builds are a lot of the time:
Builds can be fully reproducible. Resources are only available over the network if a checksum is provided to identify what the resource is. All of a package’s build time dependencies can be captured through a Nix expression, so the same steps and inputs (down to libc, gcc, etc.) can be repeated.
Containerization has other advantages though (security) and you can actually use nix’s reproducible builds in combination with (docker) containers.
I programmed some creatures. They Evolved.