Having Ubuntu on Desktops, RedHat on some corporate servers, Debian on others, Pine in VM's, raspberian on rpi's, openwrt on routers, Android on mobile phones, yada, yada, yada doesn't seem to have done Linux any damage. Quite the reverse. It's almost certainly a major factor in Linux wiping the floor against Windows. Microsoft doesn't have the manpower to turn Windows into something that address all those niche's. While it's true Microsoft have succesfully defended the desktop for now, they have in the mean time lost the war on every other front.
So, one can argue that the quality of Windows is changing, but building an operating system is no easy task. And Microsoft’s commitment to backwards compatibility is quite an achievement.
I don't mind, really, Windows 7 isn't even supported anymore. But Linux would install without a second thought and run the most updated version of almost everything (excepting things like packages not compiled for arm yet or something). Saying Windows should get lots of credit for backwards compatibility feels a little disingenuous when compared to Linux... which actually still runs on hardware from the 90s.
When people talk about Windows backwards compatibility they're mostly referring to running on apps on a new OS, not new apps running an old OS. I bet you could get very old versions Microsoft Office running on Windows 10. I've run Visual Studio 6.0 on a Win10 machine no problem. And yeah linux nowadays has a lot of drivers included with the kernel (I've bene shocked at some of the supported hardware) but vendor provided drivers of often super outdated. I have a decent chance trusting old driver binaries to run on windows. On Linux you likely have to be a driver developer yourself to just to get some vendor's driver source for an old 2.X kernel to compile, let alone run.
It has been a very, very long time since I've run into hardware that I had any incentive to install vendor provided drivers for in order to get a computer running with Linux, with the exception of VMWare kernel modules and NVidia drivers, but Nvidia cards still run with noveau so the computer will still work so that you can get the proprietary drivers. And VMWare is proprietary software, so that's no surprise.
I just have not done it for actual hardware other than Nvidia graphics cards in at least a decade. Maybe I've gotten lucky in the hardware I've bought or something, but I haven't had any drivers broken badly enough that I even would file a bug report except for my Nvidia proprietary driver that is buggy as heck.
But I accept that my experience is also an anecdote.
Of course Windows excel in apps backward compatiblity better than Linux (it's not about hardware). You can't just run old Linux games CD. You would have a better time using Wine with Windows version of the game.
> Ubuntu on Desktops, RedHat on some corporate servers, Debian on others, Pine in VM's, raspberian on rpi's, openwrt on routers, Android on mobile phones, yada, yada, yada
?
Red Hat is IBM nowadays.
Android might just be running on Fuchsia in a near future, and Linux kernel is not exposed to userspace, so it is pretty much irrelevant what Android runs on.
BSD, NuttX, RTOS, Azure RTOS, Green Hills, QNX, Zephyr, Harmmony OS, yada, yada, yada
I doubt Shuttleworth would consider selling anyway, least of all to Microsoft.
As long as the system collects and exfiltrates data without me explicitly allowing this, and does OS updates just before somebody wants to give a presentation, it is not the feel of running Linux. The feeling of running Linux is the user being in control of his/her device and his/her data. A 1990 MS DOS installation is closer to that feeling than any recent Windows.
So basically that leaves IBM and Microsoft calling the shots what Linux is supposed to be.
Plus in what matters in embedded space I will give about 10 years for MIT OS like Azure RTOS and Zephyr to wipe the floor of GPL based Linux distributions.
Never heard of Azure RTOS before, but it seems MS went and bought Express Logic. That's quite big.
But it doesn't seem to be MIT?
https://github.com/azure-rtos/threadx/blob/master/LICENSE.tx...
Either they're doing something unique enough in hardware that you pay for the development seats and special interfacing hardware, or you go with a generic part and get to use all the cheap/opensource tools.
RISC-V strategy make sense, first standise the core that allows you to run all tooling. At necessary thigns like floats and so on. And the move on into more interesting extentions like Vectors.
If a company does something unique, the can take the standard compiler and have standard way to add an extra extention.
Of courese because the world is not perfect you will have some sudo standards and companies that have their own version of some of these.
Profiles is a way to manage that and to find configuration of extentions that often work together for desktop, embeeded or something like that. Seem relativivly well thought out for something that has such braod application.
In theory yes, what happens in practice is for your application, you only need a few operations from N different extensions and now you have to implement all those extensions, if you want to be compatible.
The alternative is you develop the few ops as custom isa and break compatibility.
So you can either be non compatible and lean or compatible and bloated. Guess what will processor/chip designers will prefer given the energy constraints.
> So you can either be non compatible and lean or compatible and bloated.
That's a waste overstatement. The profiles are optimized for specific fields already and you have to evaluate if you want to take advantage of all the software and infrastructure around that profile of if you want to redo all the work just so you can cut out a few specific instruction.
You act like as if every company makes its own costume chips with the minimal set of instructions they need, but that is about 0.01% of the market or less. For the waste majority of use case simply not required and standard embedded profile is perfectly reasonable. And the commercial chips and commercial software will also target that profile.
If you really want to redo everything with your costume chips and compilers, software and so on then that's your choice and RISC-V should not prevent that.