Agreed, but it does mean the evidence at her trial was not stall sufficient to prove guilt (beyond reasonable doubt).

Ahhh nice, I have thought about trying out Kakoune as it supports plugins. Do you use many plugins/find them useful?

Helix does have a pipe command also.

Yeah I agree, I like that aspect too!

I use Helix

TLDR: Yes I think helix is worth trying out. It has some missing features but it is an amazing piece of software.

Yes I use helix daily. It is very fun to use and you can do many things faster. It is particularly good when navigating a (large) codebase you know fairly well. You are able to jump around and find/edit relevant code very quickly.

Compared to vs code:

• it is much faster and more minimal
• It might be harder to get things up and running than in vs code, e.g. to get auto-completion working in helix you need to have the LSP for that language installed. It can be a bit confusing if you have never done it before but it is easy once you have done it a few times.

Compared to neovim I think it is:

• easier to learn
• slightly faster - especially with large files
• you will have a much smaller/simpler configuration. AFAIK Helix has more features working out of the box than neovim (file picker, lsp support ect) and needs less configuration to get things to a workable state.

The downside of helix compared to both neovim and vscode is that it does not have plugin support yet so you will need to use other tools in combination with it to get an equivalent experience. Here are some tools that are commonly used with helix:

• yazi - terminal file manager
• gitui or lazygit - terminal git user interface
• zellij - terminal pane manager

Helix really shines when:

• performance matters - I have edited files with millions of lines and had no trouble on codebases where my colleagues IDE's become very slow.
• You want to use multiple cursors at times
• You want a simple or no configuration
• It is taking too long to learn the vim keybindings - vim keybindings are more concise but less intuitive and harder to learn

I recommend you use the tutor (hx --tutor) for a few minutes each day to learn the keybidings.

Another day older and more tech debt

https://snowflakeos.org/ - this project is focused on building an easier version of nixos including a GUI software store based on gnome software.

edit:ooops I meant to respond to @[email protected] here

anything I tried getting from their repos was always way further behind the mac OS homebrew or Debian apt versions.

Nixpkgs are the most up to date of any package respiratory source

It is likely that you were using the current 'stable' channel that does not have the very latest packages. The 'unstable' channel does have the very latest packages and is what I think most people use.

nixOS is really slick in concept, but has a steep learning curve to get it properly customized as a daily driver. The learned skills don’t really translate outside the nix realm either, so I decided it was too much effort for my use case. I love this concept as a way to build reproducable servers or workstations tho, so I’ll def be playing with it again.

I totally agree, I wish it was easier to learn.

You should check out zig, its compiler can even be used for c/c++. If you have time to listen to an interview, this developer voices interview on zig explains some of the advantages of this: https://www.youtube.com/watch?v=5_oqWE9otaE&t=3970s

Putting aside the speed uv has a bunch of features that usually require 2-4 separate tools. These tools are very popular but not very well liked. The fact these tools are so popular proves that pip is not sufficient for many use cases. Other languages have a single tool (e.g. cargo) that are very well liked.

If you do multi stage builds (example here) it is slightly easier to use venvs.

If you use the global environment you need to hardcode the path to global packages. This path can change when base images are upgraded.

Sure, but in the case where you upgrade python and it affects python packages it would affect global packages and a venv in the same way.

upgrading your base image won’t affect your python packages

Surely if upgrading python will affect your global python packages it will also affect your venv python packages?

you can use multi stage builds to create drastically smaller final images

This can also be done without using venv's, you just need to copy them to the location where global packages are installed.

He is a front end dev/engineer and he mainly talks about the UI (which is his expertise).

Here are their repos: https://github.com/zen-browser

and here is a video from Theo on youtube looking into zen browser: https://www.youtube.com/watch?v=tKM2N4TQHQY

I don't think they have anything to do with each other, it looks like prefix.dev uses conda packages.

Yeah it is, eventually they want UV to have feature parity with rye and rye will basically just be a pointer to UV

Early on uv was only trying to replace pip. This latest update is a big step towards becoming a poetry (and pyenv/pipx) replacement too.

It worked for me with just: virtualisation.libvirtd.enable = true; in the configuration.nix.

Stable channels provide conservative updates for fixing bugs and security vulnerabilities, but do not receive major updates after initial release.

If you want up to date packages then use the unstable channel.

Nix has the most unique packages and the most up to date packages of any Linux software repository. It has substantially more fresh packages than Arch or Alpine (which you say does a better job in a separate comment).

Source:https://repology.org/repositories/graphs