If you are going to learn computer architecture, you will learn something cheap you have on hand
If you are going to learn computer architecture, you will learn something cheap you have on hand
Assuming performance and software support is comparable. Which obviously won't be the case for a long long time.
But there are few things as irrelevant as the CPU instruction set. (Part from specific extensions, like AES support enabling quick crypto etc.)
The technology is what people know. Using a different SoC board, camera, ... requires adds more time to gain the same level of knowledge.
Doctors will latch onto a single product solution so they don't have to spend the time learning how to operate an alternative. Hospitals need to stock consumables based not on the best products but on what doctors know.
Airlines retain the same air crafts to reduce time spent learning to operate an alternative. Boeing marketed this as a sales feature with 737 MAX, no extra flight training required!
Software developers will often stick with the same language, even though others better fit the domain problem. Few seem willing to take the time to try and play with new concepts, languages, and operating systems.
Trying new and different things drives innovation not the world.
Some things will surely change because the hardware backed features work in a different way, but mostly it will be similar enough.
Going from a raspberry pi to an orange pi could be a much bigger leap than switching to an raspberry with RISC-V that has mature software support.
I’m going to have to disagree with that statement…
… but only because I’m in the middle of goofing around with ARM assembly on an RPi as we speak.
The Amiga 500 didn't make people stick to the m68k. They went IBM PC as did everyone else.