There's no reason btrfs shouldn't work for every use case.
That said I think the slight performance gains of ext4 over btrfs make it worth sticking to ext4 for games. Imo it's similar to as if you had you main system on an HDD but ran games off of an SSD; that's how much faster it feels.
I would install games to a separate ext4 partition but steam to btrfs (for configs) in that case.
I agree. We've let the standards for what is good drop.
I think it's mainly because the "just works" mentality has become infectious among engineers. It's one thing when just starting out, but as you learn more and gain experience you should care more.
People do the designing and architecture and programming just because it all pays well, not because they have a love for the craft.
I think the second, slightly less strong reason is because many engineers do not know how to effectively communicate with management when something will result in terribly written software and just do it anyway. Another skill I see less and less amongst my brethren.
This is already how the military works BC they lost the source code for ancient machines. They've gotta now hire reverse engineer researchers to help out
I like FreeCAD, but I've heard people complain about it.
I'm not an ME, so I certainly don't make use of all the CAD features needed, so maybe that's why I don't get the complaints. Still, it suits my needs which mostly involve modeling PCBs and building enclosures around them.
I have also been toying with the idea of some simple 3D modeling, like making custom parts for projects around my house
I think that FreeCAD and Blender are probably fine for this.
Example of something I've made and printed the enclosure for via FreeCAD: Fight Key Wide. It uses parameter-based design and includes some design touches like screw-holes and bezels which aren't purely simple geometry, so FreeCAD gets a pass in my book.
If you look at the GitHub linked on the project page, it has the enclosure files which you can check out in FreeCAD if that helps you get started.
I've been using a custom version of paleofetch for NixOS for a while, but I decided to write my own clone of neofetch in Rust when I heard about the archival just for fun.
It has (or I suppose will have) parity with everything neofetch can output, supports dynamic plugins, is super fast bc compiled, and looks up information using asynchronous fetches. It's configurable via a config file (JSON) to choose what you want to show (I think this is better than using CLI options for this kind of app).
I have the app's framework/architecture up and running, I just need to finish implementing the rest of the data lookup and add more distro logos.
Once I get the data lookup feature complete, I'll make the repo public so people can add their distros' logos and use it, but I'm treating this as more of a pet project, so I doubt people will be that interested in using/contributing since plenty of other fetch programs exist, so I don't care if it lives or dies; it's just fun to make things :)
Tenatively named fetch-rs, but I'm sure something like that already exists.
There's no reason btrfs shouldn't work for every use case.
That said I think the slight performance gains of ext4 over btrfs make it worth sticking to ext4 for games. Imo it's similar to as if you had you main system on an HDD but ran games off of an SSD; that's how much faster it feels.
I would install games to a separate ext4 partition but steam to btrfs (for configs) in that case.