https://docs.microsoft.com/en-us/windows/win32/wic/-wic-lh
https://docs.microsoft.com/en-us/previous-versions//dd443207...
https://docs.microsoft.com/en-us/windows/win32/shell/customi...
and in macOS,
https://developer.apple.com/library/archive/documentation/Gr...
https://developer.apple.com/library/archive/documentation/Mu...
Although, yes I do concede it is more complex to implement, the way to do it depends on what kind of data type we are talking about, and it only works properly if the applications actually make use of the OS frameworks instead of doing their own thing.
And as expected with the GNU/Linux "desktop", nothing does exist that comes close to it.
In contrast, on the Amiga, I knew about Datatypes out of the box as they were written up in the user manual, and pretty much the whole developer community got on board with them. If an app used DataTypes it was a feature that the user knew about.
The Amiga community seemed much more unified than today with respect to using all the latest features of the OS. Even the smallest public domain utilities provided AREXX ports so the user could script them.
It can be images or sound, but also text, or anything else. E.g. here's a small sample of datatypes from Aminet, excluding anything sound and graphics related:
* Datatypes for transparent decompression
* Datatypes for syntax highlighting
* Datatypes for parsing document formats (word etc.)
* Assorted hypertext datatypes
* Assorted datatypes for showing debug information and structure of various binary formats, like executables.
The Core Audio stuff is definitely datatypes though - converting things to a common backend format for apps to use.
The peak of this was ActiveX; in Microsoft's world around 2000, they really wanted you to be able to embed controls and programs in web pages and then put those web pages everywhere, including on the desktop background ("active desktop").
The problem of running third-party code inside your application is not just security but it tends to crash bady and put the name of the hosting application on the crash. Eventually Microsoft got so fed up with that, especially in the kernel, they built a system where video drivers could crash and restart while the OS kept on trucking, and use of COM has faded.
COM is pretty much alive and was modernised with .NET type system.
The mistake was implementing this stuff in C++, which is way too fragile on its own. Had they built a separate VM to manage requests for these objects, it would have been no problem: VM crashes, host app just restarts it. But Java did not exist yet and VMs were not really a thing, resources were too scarce.
I do think the ideas behind COM/OLE were pretty good, unfortunately real development on desktop OSes basically stopped mid-'00s so we might never know what it could have been.
Selecting menu items without closing the menu.
Toggling selection status of selectable icons (same as control+click in modern GUIs).
Changing the length of text selections (same as shift+click in modern GUIs).
Sadly, modern GUIs seem to limit themselves to two mouse buttons. Adding "adjust" would improve productivity if you had a three button mouse, and you could ignore it if you lacked mouse buttons and not be any worse off. Maybe there are other good features from early OSs we have forgotten.