Re: Planned obsolescence ? (*BSD, Rust)

> Yes, 20 year old hardware is looking ancient and retro.
To specify, I was refering to x86-64-v1 hw when I said "reasonably large 
amount of users". As I wrote already, that hw is still in mainstream use 
in the form of used Core2Duo-era office PCs that gained a second life as 
someone's home PC.

> There is no practical reason to use Linux on any of those [...]
Except for homelabers, in enterprise environments (legacy software!) or 
lab environments (specialised hardware peripherals), etc.

> a Pi 5 soundly beats any of those systems ever made
And a Threadripper PRO 9995WX based system soundly beats any Pi 5. So 
going by your logic there isn't a practical reason to run Linux on a Pi 
5, because there is a more capable system out there. That logic isn't 
very sound, yk?

> There are certain advantages to going with the language more people know and use.

Yup, that's the reason OS code is usually written in C.

> Part of it is that systems that don't support Rust are going to be less and less capable of using modern software.

That only means that in the future you'd have to have a highly 
specialised Rust-dev team in any major OS-related project. And for what 
purpose? Just because everyone does it.
It is what is going to happen eventually, so yes, Rust should be 
supported, but for what it's worth it should only be used if it actually 
makes sense to use it IMHO.
Use it to write a suid binary? Sure, memory safety! Use it to write a 
program that only handles data streams, have 17 times slower performance 
and close the bug because now it's only 1.x to 2.x times slower than the 
C implementation? Eh.[1]

Cheers, JD

[1]: https://github.com/uutils/coreutils/issues/8573