You’re provided with an API set that is optimized for your vertical. What is the problem with fragmentation? If you only target a single vertical then there really isn’t any problem. Over time this causes more divergence unless explicit (and expensive) measures are taken to converge APIs. The outcome is a set of platforms that only share APIs by the fact that they started off from a common code base. But it becomes a problem if there is no systematic approach and specialization happens at every layer with little to no regards for corresponding layers in other verticals. Of course, there is nothing wrong with offering specialized features in order to cater to a particular need. NET Platform isn’t a single entity but a set of platforms, owned by different teams, and maintained independently. This yields to fragmentation because the. Since then, we’ve repeated this subsetting exercise many times: Silverlight, Windows Phone and most recently for Windows Store. It included the entire vertical: a runtime, a framework, and an application model on top. The compact framework was a separate code base from the. NET Framework that fit within the footprint of smaller devices, specifically Windows Mobile. NET Compact Framework which was a subset of the. NET Framework in 2002 there was only a single framework. This helps to motivate some of the decisions and ideas that resulted in the creation of. NET Coreįirst let’s look back to understand how the.

NET Framework, and what this means for cross-platform and open source development. NET Core, how we’re going to release it, how it relates to the. In this post, I’ll provide an overview of. I also promised to follow up with more details on. NET Core will be entirely released as open source software.

Endless space mono framework