[Windows Phone 7 General] speed_pour:
Not sure of the details, but I remember reading a while ago that there was technically no true "sleep" with WP7 in the context that WM uses. The short description I read makes it sound like WP7 always has the device awake but shuts down any thread that's not necessary for basic function when the screen goes off as opposed to the WM model of shutting down all threads and allowing components like the radio to send a WakeUp notification.

Sure, if you say anything in a ridiculous way and out of context, it sounds bad. I'm not saying anything so absurd as that. But there have been criticisms for years, frequently about the desktop versions, but I've seen some about CE as well. The complaints are that MS spends too much time and resources keeping old and deprecated APIs functional despite the fact that no software still makes use of it and all it does is bloat the OS causing higher RAM usage and frequently consumes more processing power. As I said before, I don't think the best choice was to completely wipe out the old and shove in the new. My reference is that MS needed to bite the bullet and cut out the 1/3 of the API that's deprecated and useless and enrich it with something new and useful...I didn't suggest the wise choice was to throw out everything though.

See, it's not helping anybody to get rude and demeaning. I've been programming for well over a decade (even back to the PocketPC) and I was also using .Net 1.0 when it was in Beta 1. I'm more than aware of how IL works and the performance hits, but thanks for dragging the level of discourse even lower. Now, for the obvious counter...anybody who used the Compact Framework knows that it was severely lacking in functionality and performance. See, I agree, their new approach solves nothing (actually makes it worse) for functionality, though silverlight will be welcomed for UI purposes. Really, you took the smallest part of what I said (that MS clings to backwards compatibility even when it starts hurting) and took it to be the fundamental belief in an opposing argument...I was just saying that some will welcome a fresh start for certain reasons, not that it was a good idea or that people should be happy about the way it's going to be done.

First, in that post I didn't say it wasn't CE at the core, in fact I didn't reference CE at all. I did reference WM, which is a relatively gargantuan layer built on top of CE. That's a pretty important distinction. The Windows Mobile layer is inefficient and it does have a lot of problems.

Second, just to restate. I don't support taking away native coding, I think that's ludicrous. I don't support killing backwards compatibility, though I would get behind ripping out severely outdated APIs. I marginally support ripping out certain parts, including about half of the WM layer and anything that even mentions the old Today Screen.

Oh thank you great lord for reminding me that I haven't a right to a point or opinion. Geez, I'm just suggesting people stop slamming on others that consider a lot may happen after the first device hits shelves. There's no reason to get hostile and rude, just say that you're only interested in the day-1 aspect and let others discuss both the short and long term. Sorry, but point doesn't stand...People want to discuss it, so why tell them not to discuss it?