4 ms·
>Windows Arm That's both an obscure and a complicated OS/Arch combination. >Intel abandoned Linux I don't understand, Intel never maintained Linux. >C being
by TZubiri 1y ago
>Windows Arm
That's both an obscure and a complicated OS/Arch combination.
>Intel abandoned Linux
I don't understand, Intel never maintained Linux.
>C being unpopular
Lol
- Ygg2 1y ago> That's both an obscure and a complicated OS/Arch combination. Ok. A more realistic example. I want to develop a Windows game, because that's where the audience is. And I want to develop my game in Rust, because I know it better than C++. So, I need a tar/zar/mar library that exists on Linux as a C lib or Rust native library. My goal is to finish the game but don't care about performance or even CVEs that much. > Intel never maintained Linux They definitely did maintain several drivers, and Clear Linux Distribution. But I was talking about their overall strategy. They are pivoting to "Intel first" mantra, sacking many Linux driver maintainers. https://www.theregister.com/2025/10/09/intel_open_source_commitment/ https://www.theregister.com/2025/10/09/intel_open_source_com... > Lol What niche is it popular now that hasn't been devoured by C++, Java and others?
- int_19h 1y agoI wouldn't say that Windows/ARM is that obscure anymore, not when there are quite a few laptops on the market with it. But, by the same token, it's not an exotic dev platform. The compilers are there, the libraries already have to compile on Linux/ARM as well as Windows/x64, which means that the same C code will usually compile and work just fine on Windows/ARM. So yeah, no, that's not a valid reason to rewrite it in Rust.