Yeah I agree, I am sure they are missing some obscure stuff. But in practise it has everything that I use and there has been no need for me to touch flatpak/appimage/snap

object oriented

Python does have OOP but you are not at all forced to use it. You can write code in a functional or even procedural style.

typing

I do hate that python doesent have proper support for typing but I think weakly typed variables will actually help beginners as it is less to think about to start off with.

indentation

I think there are pros and cons here. In other languages it is considered good style to use indentation anyway.

I’m sure it is difficult to teach a large class like that though. It was hard enough for me to learn with a much more favourable teacher to student ratio than you probably have. Sorry but honestly I do sympathise with admin as well.

yep, I mean a GUI based software centre

NixOS:

• Largest and most up to date package repository (no need for flatpack/appimage/snap ect)
• Reproducible
• Declarative
• Rollbacks you can select at boot time
• No dependency conflicts

I think it will easily be the number 1 distro if/when they can :

• the steep learning curve (e.g. have a gui installer EDIT: As in a GUI software centre)
• documentation
• have more tools use nixos and have nixos in mind (e.g. there are a couple of tools that didn’t work for me because of specific C libraries not beeing present/configured on nixos that are present on other distros. some libraries implicitly expect these to be present).

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.

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.

OH wow didn’t realise you could post to a lemmy community like that!

Have you set android autofill framework to use bitwarden?

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

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.