There’s also a whole lot of abstraction layers in software these days. All kinds of frameworks, no code platforms, scripts and engines ask introduce their own delays when running software, all added to make time to market a bit shorter or just because of some tech fetish.
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.
There’s also a whole lot of abstraction layers in software these days. All kinds of frameworks, no code platforms, scripts and engines ask introduce their own delays when running software, all added to make time to market a bit shorter or just because of some tech fetish.
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
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.
.Net