I’m a software engineer at a large company you may not have heard of, but you almost certainly know at least one of their brands. Abstraction layers are all over the place; they’re not a symptom of open-source software, they’re a symptom of lots of modern software.
Well indeed, if the closed source project has closed SDLC that’s the definition of developed and governed with internally defined goals and abstractions
Windows OS updates and releases aren’t subject to this as it’s closed source
Whether human or machine, external factors are all internally decided
Why do you assume this can’t be an issue in a closed source?
Describe the abstraction layers of a closed source project in the context of Microsoft
You can’t, unless you work for Microsoft
There’s market forces, which is not what you described; rather tooling and nuance specific to software development
When Microsoft controls the input and outputs, it’s a closed loop affected by Microsoft governance, not random tools, systems or transparent inputs
.Net
Ah yes, the open source dotnet as an example of closed source abstractions
https://dotnet.microsoft.com/en-us/platform/open-source
You wanted an abstraction layer, I provided one.
You shared an open source project. Comprehension is a skill
I’m a software engineer at a large company you may not have heard of, but you almost certainly know at least one of their brands. Abstraction layers are all over the place; they’re not a symptom of open-source software, they’re a symptom of lots of modern software.
How do external factors affect closed source systems, when the entire lifecycle is governed by Microsoft
Because even closed source systems don’t exist in a vacuum?!
Well indeed, if the closed source project has closed SDLC that’s the definition of developed and governed with internally defined goals and abstractions
Literally the definition of