More windows bullshit: WinSxS and .NET framework CLR optimization service

This thread belongs to soger.forumgeeks.net

soger	2011-09-26 21:49 GMT \| #1
Comments: 42	A while ago I've posted a comment about how pathetic Windows 7 was. Well, you know there's more where it came from! I finished my last post with WinSxS (windows side by side assemblies). For those, who don't want to go into details, WinSxS means that windows stores every version of every DLL and as more programs are installed your winsxs directory will unstoppably grow until it eats up all the universe. Take a moment to think about how stupid that solution was... It would be even better if the DLL "system" didn't existed at all and every application would ship whatever they need. I've just read on wikipedia that runtime libraries in visual C++ 2010 no longer use this technology; they include the version in the DLL file's name. HOW HARD WAS THAT? It took, I don't know, maybe 25 - 30 years for Microsoft to figure this out, that is quite an achievement! Now all they have to do is keep track of which program is using which DLLs and clean them up when they are no longer used. But I wouldn't hold my breath until they do, it may take another 30 years. But when they do think of the possibilities, maybe the day will come when one guy at microsoft will realize what that flashing (usually red) led means on their computer and THEY WILL STOP WASTING HARD DISK TIME. There is another stupidity I keep bumping into. It is called ".NET framework CLR optimization service". Wow, that sounds really professional. If nothing else, microsoft can name their products. The forums and blogs are full with people complaining about something called mscorsvw.exe which is eating up all their processor time. So what's the solution? Just run ngen.exe executequeueditems. Unfortunately the problems start here. For one, I have four files called ngen.exe and the other thing is that the 32 bit version runs for about 3 hours and the 64 bit version for another 6 hours. That's 9 hours of wasted time and electric bill and you have to do it all over again if there is a .NET framework update. Jesus fuckin' Christ; is my computer a mainframe that compiles stuff all day long? You can almost compile a functional Linux system in that time. It's simply bullshit. Untalented programmers creating reckless programs. These things your computer is compiling should have arrived already compiled from the update repository and don't let anyone convince you otherwise. And by the way system stuff shouldn't be written using intermediary languages, they should be written in C or C++ for maximum performance and dynamically linked in. It's not that hard, perl has been doing it for at least 17 years (see: DynaLoader, XSLoader). Unfortunately there is no proper bug reporting system, no place where to discuss issues like this. This is what happens when the only motivation behind creating programs is money. So all you can do is sit back, take a deep breath and keep starting the ngen.exe files until all of them says: All complication targets are up to date.