Oh nice. gdu really is ncdu, just faster (on SSDs).

Link for lazy people: https://github.com/dundee/gdu

Can someone explain why this would be even slightly useful to anyone?

How does one type without a and z?

This is the way. Docker (& compose) are not flawless, but they are predictable and useful enough for all my needs.

I currently have around 12 containers running on my server, all trough docker compose. Only thing I use nix for is providing tools & their configs. And also restic backups.

Documentation should be generated from code imo

I agree, this is an anti-pattern for me.

Having explicit throw keywords is much more readable compared to hiding flow-control into helper functions.

That’s right. Let’s return to basics, to the first programming language we learn as developers: Pascal. Well at least I have, I assume everyone does too.

/s

Maybe search for this on kaggle? Or scrape Wikipedia?

This is the major reason for me. I really liked yaml, because it is way more readable to me than JSON. But then I kept finding new and more confusing yaml features and have realized how over-engineered it is.

Yaml would be great language if it had its features prunned heavy.

Oh, i have to try these out to see if it effects my development cycle. I do notice that cargo check is super fast, but cargo build takes a long time. So codegen and linker could be the source of slowness.

For a clean build: number of cores (because cargo builds each crate dependency in a separate process), for a build of your crate only: single core perf.

For me, switching from chrone to ff around 3 years it felt the opposite. Ff opens so much faster. Also scrolling is way smoother.

This is all hard to do because it is hard to determine people’s race on lemmy. Some usernames give it away but most don’t. And I don’t go snooping trough their post history to find that out.

Woah, you are old. I use nixos btw

In my case, it just worked, on two machines. Just added steam and lutris into the config along with two other options recommended for gaming and it worked.

If you have a working system and no wish to ever install anything new, you could run it indefinitely.

It wouldn’t get any updates after some point and after ~10 years some websites would stop working because they would be using some new standard that is not yet implemented in the browser on your machine.

To update to a newer version of NixOS, you might need to change config slightly, and that requires you to know where configuration is and how to read error messages.

To install something new it is easy in 70% of cases and really really hard in the remaining 30%.

The answer depends on technical ability of your partner. In any case, they should always be able to login and extract all the data they need, so they can then reinstall, say plain Debian.

This could also be done with help from a Linux versed relative/friend. So you should leave a bit of documentation behind.

Other than that, don’t optimise for the worse case scenario. It will leave you with suboptimal system most of the time.

Is this a threat? 🤔

It started as actual unpublished technical descriptions of underlying technology.

Why would you not be upgrading due to a new feature of python? You don’t like new features or was that a badly wordered sentence?

If they made that, they could also make it so one can pay 10x more for each additional icon.

So 10e for one, 100e for two, 1000e for three and so on.

This would allow us to recognise all people seeking attention by flashing money very easily. Bonus points if we are able to filter feeds by number of icons.