Monday 27 July 2009 - Filed under opinion
I hate Visual Studio 6 with a passion. I gave Visual Studio 2010 B1 approximately 3 hours on my box before I decided I hate it, too.
A whirlwind tour of the exciting new breakage in this version:
- Flash rewritten code editor in WPF. Wait, I thought WPF was unbearably slow? Indeed, that turns out to be correct. The code editor is now unbearably slow. It’s alright though, because you get a stupid gradient painted behind your selection now. And the caret likes to be gray sometimes and black other times. What’s going on?
- External Dependencies is back for C++ projects. This was a broken annoyance in VC6, and it’s a working annoyance in VC10. The IDE will take a short pause randomly and then crap out a folder you *can’t hide* in your project node. Give me a way to turn it off, or hide it, or whatever. I don’t care. But at least it doesn’t get stuck after `basetsd.h` like VC6 did.
- A C++ console app’s main function must now be called `wmain`, at least with the default settings. If you compile as C, then `main` is acceptable, as it damn well should be. I guess this is just the latest victim of Microsoft’s neverending crusade to break C and C++ development with their tools.
- There’s now twice as many useless options in the C++ compiler settings dialog. Many of them don’t seem to work in the “All Configurations” view. I have no idea how you break something that (1) was apparently *completely generic* and (2) worked fine for 4 releases of your product, but they did it. Maybe it’s just what happens when you rewrite the world in WPF.
- You can’t install much of it onto a disk other than your primary system disk. 2.2GB seems to be as small as you can make that particular impact, with about 700MB of stuff put on the disk you asked it to use.
- There’s built-in code metrics assessment, which is available on projects on which it *doesn’t work* – like native C or C++ projects. Surely they could avoid offering the option when you’re not compiling with /CLR, rather than chugging away for a few seconds and *then* telling you you’re dumb for asking.
- There’s a very nice UML modeller. That might be useful for architecture-types who like to draw software rather than write it, and so end up “architecting” over-complicated steaming piles of … sorry, that’s not what I’m talking about today.
- The test tools are still slow. On one of my non-windows projects, my “test framework” is a pile of shell script that discovers the test definitions in the sources, compiles each test into an isolated executable and runs it, collecting pass/fail results. That’s pretty slow, since it involves invoking the C compiler for each test. Well, the VS testing tools are STILL SLOWER. Even on .NET code.
- I suppose this one is my fault for installing Team System, but half the IDE seems to be architect crap. There’s half of project, most of Visio (actually, it’s better than Visio), and countless buzzword-compliant pieces of junk that I don’t care about. Maybe they’re important if you’re high on RUP or CMMI or something, but for a small team working on small hardcore software, they’re a complete waste of time. And memory.
- In general, the IDE is sluggish. Sure, it’s pretty, but the performance makes Eclipse look great by comparison.
In summary: I’m sorry Visual Studio 2010, but it’s not working. You just don’t perform.
2009-07-27 » admin