Components are the foundational building blocks of software running in Fuchsia. Each component is a composable, sandboxed module that interacts with other components through capabilities.
Mostly because they didn't got the memo and think .NET replaced COM.
Which was kind of the original idea, but then with Longhorn WinDev wasn't happy with how things were going, so instead of doing like Google with Android, pushing the new stack no matter what, they worked against it.
So when the reboot that would become Vista started, all Longhorn ideas got redone as COM instead of .NET.
And since then all major APIs are COM based, eventually with .NET bindings as well.
Comments
Do people still code like this?
Yes
Introduction to Fuchsia components
Components are the foundational building blocks of software running in Fuchsia. Each component is a composable, sandboxed module that interacts with other components through capabilities.
https://fuchsia.dev/fuchsia-src/concepts/components/v2/intro...
COM+ Application Overview
https://docs.microsoft.com/en-us/windows/win32/cossdk/com--a...
Yes, Windows is mostly COM nowadays, when it isn't .NET.
Then you have XPC on Apple platforms, Android IPC and Fuschia IDL on Google's, D-BUS on GNU/Linux, and the new cloud fashion gRPC.
What is fun is that so many people say "but COM is outdated"... when I look around in Windows it is everywhere. :)
Mostly because they didn't got the memo and think .NET replaced COM.
Which was kind of the original idea, but then with Longhorn WinDev wasn't happy with how things were going, so instead of doing like Google with Android, pushing the new stack no matter what, they worked against it.
So when the reboot that would become Vista started, all Longhorn ideas got redone as COM instead of .NET.
And since then all major APIs are COM based, eventually with .NET bindings as well.
Yes, Manu's comic is spot on on this:
https://en.wikipedia.org/wiki/Manu_Cornet#/media/File:%22Org...