ori_prior

That person explicitly dismissed "advanced mastery" and thus challenging and bettering oneself or themselves as being non-inclusive. I find this attitude highly offensive, because my motivation towards mastery is not of that kind. I'm happy to include people, explain them my code, help them along towards mastery.

Software also has an ongoing quality crisis, all while being more and more influential in people's lives. That person's attitude towards writing quality software helps to deepen that crisis and is therefore harmful.

Ah, the lowest-common-denominator argument for why your code is crap. That is the reason that Python code has become what PHP was 10 years ago: The mark of projects to avoid at all cost.

WSL1 was a dead end, not because of compatibility but because of performance, especially when it comes to file system access and process operations. Windows is supremely complex in both, with things like filesystem filters, fused fork+exec+setuid+setcap+doWindowsStuffThatDoesntHaveUnixEquivalents syscalls, all of which you cannot avoid. If you layer a Linux syscall personality on top of that, things will get molasses-slow quickly.

For photo and video backups, I'm using auto-upload in the Nextcloud Android app together with my own Nextcloud instance. There are various Nextcloud apps like memories where you can get additional functionality for those photos that were synced over.

What I'm still desperately looking for is proper self-hosted full-phone backups for Android phones.

I've found ext4 to be generally unsuitable to HPC environments due to the 16TB filesize limitation. So it is the wrong tool for the job anyways. xfs all the way!

xfs has had large file and large filesystem support for ages, so it is well-tested in that regard. ext4 can do larger filesystems now, but is still limited to 16TB files. zfs ist comparable to xfs in that regard.

xfs integrates well into linux and has had excellent performance. zfs is rather odd as a filesystem and circumvents several common linux mechanisms, making it rather awkward. You need to special case everything for zfs in monitoring (sizes are hierarchical overlapping instead of exclusive), ACL support and admin tooling (volume management and partitioning is completely different for zfs, trim is weird, booting is weird). zfs performance is also lacking due to it being very odd and special-casey in the linux kernel, as well as RAM-hungry.

Me too. But the CA and browser mafia is too intertwined to let this change anytime soon.

> 3 years of security updates at least from the US release date

Which means that after an initial period of half a year of "production is still slow, you have to wait" and another half year of "we maybe start selling this to Europe now", for the device I've bought today, updates will last a mere 2 years.

The typical tax-related depreciation term for computer hardware is 5 years over here. Which is already half of what typical office equipment is expected to last. After which it is usually resold or given away to goodwill. 2016 is just 7 years back, so there will quite certainly mobile phone where the tax writeoff period isn't even through which are affected by this. Truly hilarious!

No, you are right, 60% is a theoretical maximum achievable maybe with supercritical reactor coolant. The actual maximum for existing reactors is somewhere just below 40%.

60% is feasible for e.g. nuclear and gas, if you use more than one turbine and there is a big constant temperature differential. This typically isn't the case for gas plants which are intentionally variable and often intended to be cheap to build. While at peak temperature, they might run at peak efficiency around the theoretical maximum of 60% (thermal to electric) with a multi-turbine assembly, typically efficiency is far lower because gas plants usually don't run at peak efficiency and only have one turbine.

One could discuss whether it really needs to be Rust. But TypeScript is definitely the wrong tool for the job.

The performance reference is xterm. If you cannot beat that, don't bother.

Writing the first (small) program (I think drawing a line in qbasic) that, on the very first try, went through the compiler without any warning or error and did what it was supposed to do.