What is the app?

Why? It is the same power dynamic as any other open source project that is primarily built by a company.

From what I read in the HN thread the token is only used for governance (and possibly also fundraising), it is not baked into the actual platform. I am happy to be corrected though if anyone knows more/has more details.

I agree that Forgejo looks good as well and is likely more usable than Radicle right now. But I do think there is value at looking at P2P solutions.

From what I read in the HN thread the token is only used for governance (and possibly also fundraising), it is not baked into the actual platform. I am happy to be corrected though if anyone knows more/has more details.

This actually sounds really promising!

• They are teaming up with an existing python package manger written in rust.
• These are the people who make/made ruff, probably the most useful and fast python linter.
• you basically get pip from a single binary.
• they plan to have cargo/poetry like functionality in the future.

Edit: here is a blog post from the creator of rye talking about rye and UV: https://lucumr.pocoo.org/2024/2/15/rye-grows-with-uv/

Thank you Ategon and all the other admins for the work you are doing to make this place great.

In this regard, AI-generated code resembles an itinerant contributor, prone to violate the DRY-ness [don’t repeat yourself] of the repos visited.

So I guess previously people might first look inside their repo’s for examples of code they want to make, if they find and example they might import it instead of copy and pasting.

When using LLM generated code they (and the LLM) won’t be checking their repo for existing code so it ends up being a copy pasta soup.

I think helix (or some derivative) has good long tern prospects. It has a fairly large communuty abd It is much more accessible than (neo)vim.

You could also consider: https://helix-editor.com/

It does more than vim out if the box and it has similar but different key bindings. The key bindings are more intuitive and easier to learn in my opinion.

It is missing a few features still (e.g.plugins) but I have been using helix for a while and it is really fun.

Have you set android autofill framework to use bitwarden?

Would be interesting to see how fast polars (a dataframe library written in rust) would be as it can be used in python.

Libro.FM is DRM free and lets you buy any book once a month for a fixed cost.

Nice, I hadn’t heard of that before, will check it out!

Up to you =)

I think it does fit here as it is python related

Might be worth posting this in !lemmy_dev@programming.dev as that is a community around Lemmy Bots and Tools

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?

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.

This is essentially what Nix does, except Nix verifies the external software is the same with checksums. It also does hermetic builds.

Related, this article talks about combining nix and direnv: https://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.

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.1 and a program B could depend on /nix/store/rfr0n62z21ymi0ljj04qw2d7fgy2ckrq-firefox-114.0.1 and 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).

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 reproducible 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.