Windows Core OS: intending to become Android but without updating problems?

Avatar
5

With reports of Windows Core OS further surfacing in recent weeks.

https://www.microsofttranslator.com/bv.aspx?from=it&to=en&a=https%3A%2F%2Fwww.surface-phone.it%2Fwindows-core-os-dettagli-inediti-spiegazione-piu-profonda-esclusiva%2F

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.

Comments (5)

5 responses to “Windows Core OS: intending to become Android but without updating problems?”

  1. Avatar

    maethorechannen

    Android's update problems have nothing to do with "the dependencies problems of the Monolithic kernel of Linux". Linux hasn't been particularly monolithic in decades and it's module system isn't all that different than what MS is doing.


    Android's update problems stem from OEM and telco indifference. Why bother updating your phone when they already have your money? Especially as they have a new phone to sell you. That's why I have my doubts that Project Treble will really deliver on it's promises.


    Apple are lucky. Their margins are large enough that it's worth updating older phones to keep customers happy and loyal. They don't need you to buy a new phone every 12 - 24 months (want yes, need no). What they need is that your next phone is also an iPhone, whenever it is you buy it.

    • Avatar

      rameshthanikodi

      In reply to maethorechannen:

      Telco-controlled updates are unique to the west. Here in Asia, every single phone sold is unlocked, by law. All updates come from the OEM.


      While OEM indifference may be an issue, OEMs have also expressed difficulties in delivering a new version of Android for their users, but Google ignored the difficulties faced by OEMs for a long time. I assume it was partially because Android's growth trajectory was doing very well anyway. So I would say that Google's indifference to the issue played a role as well.


      I'm actually pretty optimistic that Project Treble will improve things because Google is finally listening to the OEMs.

      • Avatar

        SocialDanny123

        In reply to FalseAgent:



        OEMs basically have no initiative to update their devices. They don’t make money updating devices. They make money selling new devices. Which is why I don’t think Trebble will work. OEMs still decide how long they update devices, especially in a market where OEM profits are so low.

  2. Avatar

    Luis Sohal

    For #HotmailpasswordResetOrRecovery Call on &&**866).(877).(9859)__++

    #Outlook Support Number

    #Micrsosoft Support Number

    #Outlook Password 

    #OutlookSupport 

    #HotmailPasswordRecovery

    #OutlookandMicrosoft Support Phone Number

    Call ***866).(877).(9859>>>


  3. Avatar

    Tech_Support

    For #HotmailpasswordResetOrRecovery Call on &&**866).(877).(9859)__++

    #Outlook Support Number

    #Micrsosoft Support Number

    #Outlook Password 

    #OutlookSupport 

    #HotmailPasswordRecovery

    #OutlookandMicrosoft Support Phone Number

    Call ***866).(877).(9859>>>

Leave a Reply