Linked by Adam S on Thu 10th Jul 2008 16:58 UTC
Thread beginning with comment 322402
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: How about 20 thing NOT to include
by ebasconp on Thu 10th Jul 2008 21:27
in reply to "RE[2]: How about 20 thing NOT to include"
Your being sarcastic here right?
Not at all!!!
.NET Framework is a very good platform in several senses:
* Abstracts several low-level things doing the application programming easier for the common mortals.
* The .NET Framework Base Class Library is a good object oriented framework (quite similar to the Java one).
* The CLR is optimized and provides a lot of nice features (including memory protection by software, garbage collection, exception handling, unified datatypes, etc. etc.).
* WCF and WPF are really powerful frameworks.
RE[3]: How about 20 thing NOT to include
by OddFox on Sat 12th Jul 2008 04:54
in reply to "RE[2]: How about 20 thing NOT to include"
OK, I can understand liking Aero. I'm a minimalist, i like simple GUI's that don't eat up CPU.
First off, Aero is disabled when any full-screen 3D application is launched (Note that this almost always excludes games that you run in windowed mode). Secondly, the Aero user interface uses so little additional CPU/memory that it's completely negligible on any system that is actually specced to run Vista. There are plenty of things to dislike Vista for, Aero is not one of them. Check out some benchmarks if you don't believe me.
http://blogs.zdnet.com/hardware/?p=107
http://channel9.msdn.com/forums/Coffeehouse/262100-Does-Disabling-A...
To quote a post in that second link, "There is only one benefit after disabling DWM as a service - several megs of RAM. But bloody "svchost" eats much more. Better to kill him." To put it succinctly, if you've got DX9 or better graphics hardware with ~256MB of video memory, disabling Aero will degrade your windowing performance.
I personally hate using any pre-Aero interface since that usually means redrawing issues when there's any sort of load going on on the system (And sometimes that's not even a prerequisite).






Member since:
2007-08-05
Why not Aero? It is a nice UI, if the users want to have all the eye-candy Aero provides... good for them... [you can disable it if you do not like it]...
OK, I can understand liking Aero. I'm a minimalist, i like simple GUI's that don't eat up CPU.
But...
Why not .NET framework? It is a good development/application platform and Microsoft promotes it.
Your being sarcastic? right?
Edited 2008-07-10 21:23 UTC