Linked by Thom Holwerda on Tue 21st Dec 2010 22:56 UTC, submitted by fran
Windows Very light on details, but this is interesting nonetheless - very interesting, and potentially one of the biggest things to have hit the operating systems business this decade. Bloomberg is reporting that Microsoft plans to announce Windows for ARM processors at CES in January 2011.
Thread beginning with comment 454440
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

"CE feature set does not compare to Linux or darwin or qnx. Yes Linux the core of Android. Darwin the core of Iphone. And QNX the core the blackberry.

Have you ever seen/used a *full* version of CE 4 or greater? (and *full* is subjective, as the platform builder lets you pretty much customise the OS completely.) The OS itself is a reasonably complete implementation of Win32 - albeit, the UNICODE version of the API. The userland lets it down, bet really, the restrictions were put in place when it was running on devices with about a couple of megabytes of internal storage, including the ROM space. I used to code for a handset with an RFID reader and the OS it used was extremely complete, if you ignored the fact that Microsoft didn't seem like they were trying to make it in to a desktop OS. It was no worse than the Sharp Zaurus SL5500, which runs LINUX and was of a similar vintage. This was 5 years ago. Things don't stay still.
Yes I have. Its not a full OS. It lacking a proper secuirty framework that darwin, QNX and Linux has. This secuirty framework side is becoming a lot more important as devices increase in number and become possible targets.

Someone else mentioned drivers - well, no one seems to have issues creating drivers for other CE based devices. In industrial use, they are quite frequently used in various applications for data entry and such. They come with a variety of interfaces and add ons.

For the simple case for a lot of items. If CE does not have the drivers we just drop it from list of OS's to use. Yes we don't have driver issues with CE since we just don't use if it has.

Apps - well, most Win32 API based apps are reasonably easy to port. At the point I was at 5 years ago, the main issues were the lack of non UNICODE API and that the OS was missing some the parts that the desktop OS had available. But, if you had the entire Windows codebase, porting those parts would be possible and so therefore most of the issues would go away. If you use DotNet, the differences reduced greatly, especially when you are using CE 5 based OS.

DotNet does not address the secuirty risks that increase the means to CE based devices to be attacked.

UNICODE issue is nothing more than a smoke screen there were many third party solutions for CE to deal with the UNICODE issue. Really thinking you were not ment to be using non UNICODE code on Windows unless it was for legacy code from 1998 and before. So by CE 4 if you were running into it your coders were crappy. Sorry its the truth. So how come you were running into it 5 years ago.

Missing some parts that the desktop OS has is the serous issue. There are quite a major list of features that CE simply does not do. Yes it was built for the Limited memory space issues that don't exist today.

Reply Parent Score: 2