News for hackers. Stuff that matters.
Re:Swift was always going to be part of the OS by wheybags on Saturday December 16, 2023 @07:06AM (#38663652)
The more time passes, the more I feel like dynamic linking of anything but plain C interfaces is just a bad idea.
Re:Swift was always going to be part of the OS by criddell on Saturday December 16, 2023 @07:16AM (#38663700)
Would you consider using runtime things like Microsoft’s Component Object Model (COM) to be a form of dynamic linking?
Re:Swift was always going to be part of the OS by rezonant on Saturday December 16, 2023 @08:08AM (#38663917)
The real question is probably "Is COM a bad idea?"

And I don't think it is. But COM itself was such a pain to deal with. Notably all of my time with it was spent from within .NET so maybe it was less painful in C++-- but .NET was at least partially designed to work well with COM. Insert crying emoji.

(Of course I think Microsoft intended us to stop using COM and instead use SOAP, but that didn't happen)

Re:Swift was always going to be part of the OS by alternative_a on Saturday December 16, 2023 @09:36AM (#38664493)
SOAP is an object access protocol. COM is an component object model. How is SOAP providing a component model?
Re:Swift was always going to be part of the OS by flohofwoe on Saturday December 16, 2023 @12:12PM (#38665883)
The only really important and surviving part of COM isn't the "component model idea", but that COM enables versioned interfaces and dynamic linking with a stable ABI for high level languages that usually don't have a stable ABI (like C++) by defining a standard of how high level language concepts can be tunneled through a regular C API.
Re:Swift was always going to be part of the OS by pjmlp on Saturday December 16, 2023 @02:10PM (#38666862)
Which is even overlooked is how similar ideas have been adopted in Apple and Google platforms (XPC, IO/Driver Kit, AIDL/Binder, FIDL/zircon), less so in GNU/Linux as not all distributions rely on D-BUS for similar ideas.
Re:Swift was always going to be part of the OS by pjmlp on Saturday December 16, 2023 @12:01PM (#38665752)
Since Vista that COM is the main delivery mechanism for new Windows APIs.
Re:Swift was always going to be part of the OS by pjc50 on Saturday December 16, 2023 @12:10PM (#38665866)
COM (a) requires dynamic linking underneath and (b) uses C interfaces underneath, or at least used to.
Re:Swift was always going to be part of the OS by pjmlp on Saturday December 16, 2023 @02:15PM (#38666909)
Only In-Proc COM requires dynamic linking, COM servers rely on processes.

DCOM, nowadays out of fashion also uses processes, and in case of exposing In-Proc COM to the network, a wrapper server process is required.