"The OS -- the features, the documentation, the learning focus, the ease-of-use planning, the designed support for school and code clubs"
It reminds me of the class a family member took recently where they were learning basic shell scripting using c-shell on a bunch of 15 year old Solaris machines. Interesting, but also somewhat harmful because they now have to translate what they have learned to linux/macos/etc should they actually get a job/etc that involves any shell scripting because bash tends to be the default.Similarly with the RPi, the install process needs custom tools, instructions, and images because the normal distro install process (which are overwhelmingly UEFI based) simply don't work. So they are basically teaching everyone how to perform actions that any students that go into IT related fields will need to relearn.
https://ubuntu.com/tutorials/install-ubuntu-desktop#1-overvi...
And there isn't an argument that they are making it simpler either, since its entirely possible to create ubuntu/etc disk images as well while still burying a proper boot/etc interface in the firmware.
So, as I said earlier what they are doing made sense 10 years ago but today looks out of place vs what everyone else is doing.
PS: And as far as the hardware, normal distro's don't seem to have problems with missing RTCs (they all enable NTP AFAIK), and none of the interfaces on the board are that weird. Mainline Linux supports GPIO, and MIPI/CSI, etc.
https://www.kernel.org/doc/html/v4.10/media/kapi/csi2.html
If those don't work on the RPi in mainline, that is where the foundation should be focusing, in order to land their drivers upstream, or provide binary packages for the main distos (or both as some vendors do). They aren't special in this regard, they are only special because instead of doing what everyone else does, they created a custom linux distro.