Originally Posted by tompsonn
Well its not technically part of an API no, if we are going to strictly take concepts from Win32. The Window Manager provides the controls for this automatically. But sure, programs can close themselves down but this is not a UI concept.
Anyway your second paragraph is where the confusion stems from as I thought you were referring more towards that
They couldn't create "better" APIs for the desktop/Win32 because well.. I could see it breaking many many programs, so compatibility was a constraint. Not too sure what you mean by "better" though.
And in some ways, they have. The CLR and .NET framework is one example with a generational GC that helps free the burden of the programmer from memory management (although not completely, but more-so than a native language, however advanced usages requiring p/invoke calls into Win32 APIs still require MM in .NET, too).
Also we need to realize the distinction between the API and the run time itself. The API provides services to invoke the run time (which as they stand now are really just a bunch of wrappers over Win32). A "better" API would not solve leaks due to poor programming (which is almost always the cause). The run time as the governor of the apps can step in which is what it does with application lifetime management, but of course there is only so much it can do.
Cannot guarantee 100% no leaks, of course not. Software will never be bug-free, but it appears to do a pretty good job so far.
Besides, if programmed properly a program will not have memory leaks. Also often the end user cannot tell what a memory leak is (unless it is obvious and hundreds of MBs of memory is being used for no apparent reason). Gadgets != Windows Runtime. Not sure what's up with that, but sure - jury is definitely out on its security.
Thanks for the informative post! Rep+
Originally Posted by lordikon
If there's one thing I've learned over the last 25 years or so, it's that change is inevitable, and that many people are resistant to it. It's one of the most frustrating things when dealing with my grandparents, they are stuck in their ways, unwilling to embrace any change, and it affects them for the worse. If you can learn to accept change, and adapt to the changes, you'll likely find that life will go more smoothly. I'm not advocating that all change is good, and that everyone should just be a pawn and accept whatever they are given, but it's a useful skill to identify which changes are here to stay and may be important, and those are the changes you might want adapt to, rather than ignore.
Why do you think it is that children adapt and learn so fast? They're malleable, they accept change easily. If you can accept change and unfamiliar things, you'll learn faster.
First part of your post = reasonable logic, except we all know where you're heading - Windows 8 is GOOD change. That is the main problem with the logic. That is your assessment and there are many valid concerns over why Windows 8 is NOT good change.
And I did learn fast how to use Windows 8. And in those cases where I didn't know at first how to accomplish something, nothing a little google search wouldn't solve. The problem is, I still don't like it. I understand the concept, I described it in my Developer Preview review (link in my sig), so I don't think I am particularly averse to change since I went right away and built a test system for it, and then still gave it a second try with the Consumer Preview, and I think it's badly implemented - and Microsoft proves me right every time they make many changes to the UI, from Developer Preview, to Consumer Preview, to Release Preview and even to RTM. Even the nomenclature they used "Preview, Preview, Preview" in all three denotes that they are not confident enough to at least call the last version prior to RTM Released Candidate, because they apparently still had changes to the UI to make.
You should have the skills to know how to identify that Windows 8 is pretty much a work in progress and that it will only be consolidated in Windows 9.
Originally Posted by Majin SSJ Eric
Surely that's just a bug though. I can't imagine that MS would intentionally destroy multitasking in the metro interface...
No, it's by design. Unless they change the design, but I doubt they will do that in Windows 8, probably only in Windows 9.