|Subject||Posted By||Forum||Category||Last Activity||Activity|
||SocialDanny123||Microsoft||Windows||3 years ago||
With reports of Windows Core OS further surfacing in recent weeks.
Operating systems such as Windows, consist of Layers (strata). The lowest is the kernel, which connects the hardware to the operating system, then the underlying libraries, the interface and finally the app. In reality layers are much more than that, but it's just to give you an idea. Windows Core OS, takes its core Windows Kernel and libraries and make them completely independent of architectures (x 86, ARM) and separates them from everything else. It is formed from OneCore , which is formed in turn by the Windows NT Kernel 10.0 and very low level and OneCoreUAPlibraries, bookstores at a higher level.
Cshell runs "on top" of Windows Core OS and is completely written with UWP API. Taking advantage of the so-called "Composer", Cshell is capable of modifying the interface elements to fit into certain sizes of screen or device input. This will allow us to not have to rewrite every time 7 times (that's right, 7 times) each component. Needless to say that this interface is completely independent of the hardware architecture of the device. But now we come to the Composer. Abstract: each device can have more than one Composer, even all, is chosen by Microsoft.
In some ways this is an interesting development going on for Windows 10. In future we could see Windows 10 become becoming what Android should have been at the start (Without all the updating problems and the dependencies problems of the Monolithic kernel of Linux). Where an OEM basically can create a composer UI for their device, but the customisations are independant from the rest of the OS architecture, this in theory can allow MS to keep updating the OS in a timely matter that Android does not allow.