Maes
I like big butts!

Posts: 8661
Registered: 07-06 |
I don't get all this aversion towards .NET. Sure, it's always inconvenient to have to install an additional middleware/runtime environment just to run ONE program that you might not even like, but in the case of .NET:
- It's an official Microsoft product, and there's definitively more than one program that uses it. It's not like e.g. those malware-ridden "downloaders" that certain "FREE online games" require you to install.
- .NET is to Windows what Java has been (and still is) to servers, linux, etc. all those years. Then again if you are among the folks that in 2011 still believe that Java is slow or bloated....
- That requirement for "Visual C++ 2005 redistributable" that pops up with far too many programs as of lately, including ZDL seems to go unnoticed. Then again, the fact that's it's only 10 MB and pretty unobtrusive to install surely helps.
The only case where I'd avoid a .NET application given an alternative, would be on limited hardware (anything under a Pentium IV and 512 MB of RAM, to be precise). In such low specs, the overhead of the framework is really noticeable. And then, I'd only avoid it if it was the ONLY .NET application I would like to run on that machine.
That being said, Microsoft has really fucked up the sizes of the redistributables: 250 MB for the full 3.5 runtime? Seriously? Compare it with the 70 MB or so for a full Java SE SDK (aka also fully usable for development). Another reason to keep framework requirements <=3.0 (which is also built-in on Vista and 7).
Anyway, this is the first time I hear of a .NET developer that is not aware of the distribution implications.
Last edited by Maes on 10-23-11 at 12:36
|