Forum Discussion
MicrosoftInking on Web Pages - Discussion
IndustrialAutomation
BTW, I have a Windows Mobile which, I, actually, really, like. It's not my 1st, either. Grabbed a Windows Mobile soon as they came available... and, stuck with them. And it, a Windows Mobile, still, does just fine, for me. The Mobile's OS updates rather than, having to update the Mobile, itself, too 
.
Cheers,
Drew
Good for you,
the apps and the compatibility level with other devices that I need only come with Android OS, which is Open source.
companies don't need to seek permission to put Android on their phones. one of them is Huawei which created the best and most powerful phones in the world and they manufacture their phones without Google services or relying even one bit on Google. that's a great thing. to have full control over your product.
HotCakeX Android was an excellent proof of concept and a terrible production implementation. The timeslice management is inappropriate for a portable device. The strategy introduced by Windows Phone and adopted by Apple is much better. Nevertheless, even on these systems, built-in software not implemented as an app is outside the law and can misbehave when inadequately tested.
The right solution is an RTOS with an app sandbox. Curiously, Microsoft just bought an RTOS, or the rights to use one (I'm not clear on that).
IndustrialAutomation
There is, now, sandboxing in Win10 Pro & enterprise ever since 1903. It is enabled where or as shown... Check its box & hit OK. Oh & Hyper-V virtualization must be enabled, also (That's in the BIOS).
Cheers,
Drew- What does Sandbox has anything to do with Web page inking on Edge browser? just wondering
- I would like to know more about timesslice management of Android and how it's bad. is there any links to articles or posts with more info?
what's Apple's strategy that's better exactly?
how can it be better than open source Android OS?HotCakeX It's not bad, it's inappropriate for a portable device. Android is a sort of JRE running on Linux.
Nitpickers will now interrupt with the news that it's not really a JRE. It is a runtime and the source code is Java, so as far as I'm concerned that makes it a Java Run-time Environment or JRE. No further correspondence will be entered into on this point, nitpickers of the world.
Back to the actual point: Linux provides process management. Linux supports concurrent processes. Android apps run in little sandboxes and the sandboxes run concurrently. The foreground app has the display but otherwise all apps are equal. This means a misbehaving app can hog the processor, or poll the GPS or the network even though the user isn't even aware it's still running.
By contrast Windows Phone and iOS apps are suspended as soon as they cease to be the foreground app. Apps that require periodic background activity can register a background process. Registration defines the amount of time required, the resources and how often it needs to run. When the app is suspended, the OS launches the background process on the required interval. If it completes and exits within its allotted time, all is well. If not, the OS sends it a warning message and it has one second to save state and exit before the OS terminates the process and reclaims associated resources. If the OS has to terminate a particular app's background process three times in a row, it is blacklisted and is not triggered again.
Some apps like music players appear to run continuously in background. The app is not running, an OS provided streaming service, playback or both are running and the app merely provides the user interface to launch it.
For Android, sandboxes notwithstanding, apps are essentially separate concurrent programs just like on a desktop system. This is fine for an eight core CPU with 16G of RAM and an 800W power supply. A fully charged phone battery would run that for about forty seconds. A thriftier approach is necessary especially if you want snappy UI.
