Linked by Thom Holwerda on Mon 9th Oct 2017 19:44 UTC

In a series of tweets, Microsoft's Joe Belfiore has revealed that the software giant is no longer developing new features or hardware for Windows 10 Mobile. While Windows Phone fans had hoped Microsoft would update the platform with new features, it's now clear the operating system has been placed into servicing mode, with just bug fixes and security updates for existing users.

I was a first adopter of Windows Phone 7 - so much so I imported a device from the US during launch week. It was an amazing operating system to use, and I loved it. Soon, however, it became clear Microsoft was unable to attract developers to the platform, and even those applications that did make it weren't particularly good - not even the ones written by Microsoft itself, which were often simple HTML-based apps, which simply weren't good advocates for the platform. As a Windows Phone user, you were always scraping the very bottom of the barrel when it came to applications.

To make matters worse, the move to Windows NT with Windows Phone 8 was a disaster. Existing phones weren't updated, and instead, only got an entirely pointless Windows Phone 7.8 update. This didn't do anything to enamour users to the platform, which makes it all the more weird when Microsoft did it again when Windows Phone 10 was released. In any event, Windows Phone 8 did mature over its short lifetime, gaining many features other platforms had had for ages. Sadly, the application situation never improved, and to this day, the Windows Store is a ghost town.

It really sucks that Windows Phone became a victim of blatant mismanagement and market forces, because I still love the operating system and its unique UI. One day, I'll have to sit down and write the counterpart to my Palm retrospective, covering the entire PocketPC/Windows Mobile/Windows Phone era.

It's been a wild ride.

Thread beginning with comment 649708
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: You think that is sad?
by judgen on Mon 9th Oct 2017 22:01 UTC in reply to "RE[3]: You think that is sad?"
Member since:

No. I mean someone used a very expensive soldering lab to change the CPU. (and ram is on the OMAP since it is a SoC)

Reply Parent Score: 2

ssokolow Member since:

SoC doesn't mean the RAM is on the chip. I know that at least the OMAP3 used in the OpenPandora and OMAP5 used in the DragonBox Pyra take separate RAM.

(It's what allowed the OpenPandora to be upgraded from 256MiB to 512 MiB very early in its lifecycle without any board redesign and what will allow them to offer both 2GiB and 4GiB variants of the Pyra without awkward "must match the built-in RAM" requirements for what chips can be used for the second two gigabytes.)

That said, there is a twist to the definition of "on the chip" which may be what you're thinking of.

Some SoCs... such as the one in my original Raspberry Pi, are designed so the RAM stacks on top of the SoC even though it's a separate chip.

Edited 2017-10-09 23:46 UTC

Reply Parent Score: 5

RE[6]: You think that is sad?
by Morgan on Tue 10th Oct 2017 15:15 in reply to "RE[5]: You think that is sad?"
Morgan Member since:

SoC doesn't mean the RAM is on the chip.

Exactly, I think judgen is thinking of PoP, or "package on package", like the BCM2835 used in the Raspberry Pi. Later versions of the chip used on the Pi were still SoC (system on a chip) but were no longer PoP, with separate RAM chips on the underside of the board. This allowed for better cooling of the CPU itself, necessary with the Pi 3's BCM2837.

Reply Parent Score: 5