Not for KDE which aims to be good for beginners.

I’ll have to come up with some examples and write something more detailed I think to explore this.

Until NixOS I was very in favor of language specific package managers and things like flatpak.

You see the conclusion of that article is that flatpaks are not repeoducible after presenting solutions to make it reproducible right?

If you care about your software being stable and secure, you should care about how easy the programming language used makes and encourages that.

People aren’t robots and make mistakes often.

The issue was closed, but a draft PR was linked… potato:

https://github.com/zed-industries/zed/pull/14034

I did this before being in emacs made it so convenient to avoid, but got bit randomly by different versions or gnu vs BSD.

woman in emacs.

I also find info pages much nicer to use after an adjustment period given I grew up on vim and man.

So they should say that it is written with performance in mind. I don’t care how you achieved that. rust, c++, assembly, whatever.

I care because performant and secure C++ is much harder to achieve while rust “shepherds” you towards it.

See https://nibblestew.blogspot.com/2020/03/its-not-what-programming-languages-do.html

I care because I know the values of those programmers in a narrow scope and won’t be as annoyed when I inevitably have to go debug the rust code instead of C.

However, that values statement was challenged by automatic binary downloads without user confirmation.

Luckily the fix is already in progress, but its concerning it was ever implemented.

This video using emacs magit git porcelain might help you see why:

https://m.youtube.com/watch?v=qPfJoeQCIvA&feature=youtu.be

Basically you can go quickly from the log to viewing diffs or any other action on commits or groups of commits and more.

I used to only use git from CLI for 10+ years but mostly only use magit now.

The model of out of process rendering in Xorg was done pre-2000s but GPUs became the norm and don’t work well this way.

Thats where we get into explicit and implicit sync right?

They were exaggerating to avoid work. Look at the PR diff to determine whether your anti-Rust bias is true.

Flatpak is worse for debugging, development, and reproducibility.

Its good for user friendly sandboxing, portability, and convenience.

This isn’t true because until the PR fixing it goes through it downloads other binaries without user consent.

What does this mean?

I extensively tested apex legends with different kernels and found a difference.

And Wayland accessibility is very bad.

I use flatpak steam and flatseal to remove user home permissions so games don’t see my files.

I’d prefer to use Nix derivations and firejail but I couldn’t get it working last time I tried.

My preference for nix expressions to flatpaks is for better reproducibility guarantees, easier introspection, easier debugging, and less duplication.

Flickering makes it true for all xwayland games such as proton until nvidia driver with explicit sync.

Disagree. They should be forced to open it up for the community to maintain it when they end support.