News for hackers. Stuff that matters.
Re:Visual Studio 2010 released by javery on Monday April 12, 2010 @11:26AM (#1259334)
Having used Visual Studio for 10 years and even written a book on it I can say I am totally tired of this huge and bloated IDE and can't wait until I am done with .NET work or MonoDevelop is good enough to switch. (it's getting close)
Re:Visual Studio 2010 released by city41 on Monday April 12, 2010 @02:09PM (#1259883)
As an ex developer on VS2010, I have to give my biased opinion that they actually took the thing in the right general direction and I actually rather enjoy using 2010 a good deal more than 2008.

I honestly don't find it to be that bloated either. it loads up very quickly, and it only loads things as they are needed. If you never once use the Entity Framework for example, nothing related to it will ever load. This is different from 2008 which eager loaded most stuff.

There was a huge push to get 2010 up to performance snuff towards the end of development, and I think they mostly succeeded.

The new support for MEF for extending things is dramatically better than VSIP, which was a nightmare no matter how you sliced it. MEF is actually quite pleasant.

I'm an ex MS employee, and so feel no need to promote it blindly. I do think, overall, it's the best VS yet. Take it for what you will.

Re:Visual Studio 2010 released by unhappyms on Monday April 12, 2010 @04:24PM (#1260262)
I have been an SDET on VS2010. The real problem with VS in the past few years as it has move away from native. Everything is managed managed managed! We have left internal (Office) and external (lots and lots of folks) customers in the dust by only building decent managed tools. That's my opinion.

What I really wanted to address was performance. There was indeed a huge push after Beta2 to improve perf. At the end of the day 2010 is still slower than 2008 and eats up more memory. I guess that's an accomplishment if sucking less is considered good. But will people upgrade? I don't know. Hopefully because that's good for me. But I am pessimistic and currently looking for other employment as the experience was that bad.

Why was it so bad? Well I feel most of the pain points could have been avoided. Management ignored a lot of the performance/memory issues last summer and had an attitude of ship ship ship with NO regard for quality. I was responsible for reporting an overall grade for the areas I tested. I reported them to be poor and fair. I also listed all the known bugs in those areas. Management boosted the rating to good on the basis that memory and performance bugs don't count.

Let me reemphasize that last point: I was told memory and performance bugs DID NOT count towards the overall quality rating of the product. This was management's attitude through most of the product cycle. We could never give an honest assessment of the product because they would challenge it and argue that it wasn't that bad.

I believe their reason was simple for doing this. They need to take the data to their managers and up the chain of command to paint a pretty picture of how great the product is. Even if that's an illusion. Basically telling the truth of product quality is punished. If I lied about quality managers would be ecstatic about how a great a job we did. If I told the truth about quality instead of thanking me for figuring out where customer pain points might be the attitude was ALWAYS this should have been found earlier. The problem is many times I did find it earlier and they did their best to bury it before the next meeting they were heading off too report product quality.

I will say this. IntelliSense is much better for C++. Even though other native tools might suck. IntelliSense teams seems to be doing a pretty good job. It has always has been my favorite VS feature.

Re:Visual Studio 2010 released by city41 on Monday April 12, 2010 @05:09PM (#1260394)
It's interesting you report such disdain with the product. I will admit I was a SQL employee working on a component that was shipping in VS2010 (there's a handful of teams that did this, Entity Framework being one of them, although I wasn't actually on the EF team, they are a pretty visible example). My team really grew to dislike DevDiv and their practices quite a bit in a lot of regards (however, in other areas I enjoyed DevDiv a lot). To be totally blunt, SQL has their shit together a lot better than DevDiv does. And to be perfectly blunt again, it was the thought of doing this all over again for Dev11 that was a major motivator in me wanting to leave MS.

And is 2010 worth the upgrade for most people? Hard to say. There's nothing in it that is truly mind blowing or "must have", it just iterates and improves a ton of stuff. I don't think .NET 4 alone is a compelling enough reason, most will remain happy with 2/3/3.5 for the time being.

With all that said, I still stand behind VS2010. I think it still came together well. I really do hope I get to use it as my day to day environment, I like it that much more than 2008. I'm actually impressed how well it emerged out of the chaos that is DevDiv :)

And yes, MS has dropped the ball on native dev quite a bit. It's definitely an afterthought. But most people who are looking to get 2010 are very much in the managed camp.

Re:Visual Studio 2010 released by unhappyms on Monday April 12, 2010 @05:21PM (#1260422)
I'll admit some of the disdain is related to the process with no consideration for the the actual product itself. The taste in my mouth after Dev10 makes me unhappy and my desire to leave MS seems to align with yours: "all over again for Dev11." Good luck in your future endeavorer.
Re:Visual Studio 2010 released by city41 on Wednesday April 14, 2010 @03:41PM (#1265920)
Yeah and good luck to you too. I can sure relate to your position. Although I'm sure the two of us were on totally different sides of a very large mountain :)
Re:Visual Studio 2010 released by mrkurt on Monday April 12, 2010 @07:05PM (#1260654)
> Everything is managed managed managed! We have left internal (Office) and external (lots and lots of folks) customers in the dust by only building decent managed tools. That's my opinion.

Good! Well, good for internal I mean. If managed/WPF/etc are the future of Windows, then MS needs to start eating their own dog food and using those techs for their apps. It drives me utterly nuts to think of all the neat tools that show up in Windows that other MS divisions flat out ignore.

Re:Visual Studio 2010 released by unhappyms on Tuesday April 13, 2010 @01:57AM (#1261263)
DevDiv makes about $1 billion for MS. Office on the other hand makes about $18 billion. So in terms of politics Office gets to decide what tools they use for the most part. Office sees it as a risk in terms of profit and hitting ship dates on time to switch to the latest stuff DevDiv is spitting out.

Rumor has it WPF is going the way of Windows Forms. It will be supported but no new features. With that in mind, think of all the UI frameworks MS has had wrapping up Win32: MFC, ATL/WTL, WinForms, WPF. Nothing seems to stick. Office just writes their own stuff that they KNOW they can depend on it being there. Duplication sure. But DevDiv is notorious for releasing things and deprecating the past "great" technology within a few years.

There is another reason they ignore the new tools: managed is slow for the client. For the server world managed is great and has won. Nobody in their right mind would write native web apps. They write the stuff that needs to be native (db, webserver) then glue the app together with python, ruby, C#, or Java (I know, a vast oversimplification of webapps).

Clients don't have the advantage of the webapps. We don't have a lot of computer to do things in parallel. Every millisecond counts to make the app appear as responsive as possible.

Why does managed suck for the client? JITing is slow and the code it generates isn't nearly as good as a compiler. NGENing is possible but still slow because of garbage collection and marshaling data between native and managed code. Little things like that add up and slow down responsiveness a lot on the UI side of things and that is what the user notices and complains about.

Re:Visual Studio 2010 released by natmaster on Monday April 12, 2010 @04:33PM (#1260287)
I don't know what IDE you use, but I use both Visual Studio and Eclipse. Eclipse is significantly slower, but it's still acceptable performance, and I like the python, hg, and remote plugins, so I find it very useful.

For C#, VS is absolutely wonderful, and I haven't seen an IDE for a statically typed language I like better.

Re:Visual Studio 2010 released by snprbob86 on Monday April 12, 2010 @05:23PM (#1260429)
I greatly prefer C# over Java. Luckily, JetBrain's Resharper makes VS almost as awesome as IDEA.
Re:Visual Studio 2010 released by dschobel on Monday April 12, 2010 @11:32AM (#1259352)
Is it slower than any of the other enterprise grade IDEs (eclipse or intellij)?

I haven't used the later in ~12 months but I don't remember them being particularly speedy in comparison.

The only things I truly find insufferably slow in VS are the visual designers which do code-gen "on the fly".

Re:Visual Studio 2010 released by rbanffy on Monday April 12, 2010 @11:35AM (#1259364)
I am always annoyed when someone says "enterprise grade". What is an enterprise-grade IDE?
Re:Visual Studio 2010 released by locopati on Monday April 12, 2010 @12:44PM (#1259624)
I say this only partly tongue-in-cheek...an enterprise-grade IDE is one that you're probably not going to use unless the enterprise paid for it (that said, I'd readily shell out $250 on a JetBrains IDEA personal license if I went back to consulting - personal performance gains more than make up the cost).
Re:Visual Studio 2010 released by dschobel on Monday April 12, 2010 @11:41AM (#1259385)
integrated tools to support full software development life-cycle: things like version control, test runners, parameterizable builds, etc.

plus the option for commercial support.

Re:Visual Studio 2010 released by albertzeyer on Monday April 12, 2010 @12:09PM (#1259483)
What IDE/texteditor does not have that? (Or can have it via a plugin?)
Re:Visual Studio 2010 released by rbanffy on Monday April 12, 2010 @07:36PM (#1260714)
Well... Notepad, for instance, is very limited.
Re:Visual Studio 2010 released by albertzeyer on Wednesday April 14, 2010 @01:49PM (#1265541)
I would not call Notepad a texteditor. It's nothing else than a textbox.
Re:Visual Studio 2010 released by javery on Monday April 12, 2010 @12:40PM (#1259609)
I haven't used Eclipse much, but when I did it felt pretty similar to Visual Studio.
Re:Visual Studio 2010 released by briansmith on Monday April 12, 2010 @01:38PM (#1259804)
Eclipse 3.4 is notable slower than VS2010 on my computer.
Re:Visual Studio 2010 released by frou_dh on Monday April 12, 2010 @02:00PM (#1259860)
I can't bear to use MonoDevelop because of the forest of unpleasant non-native UI in your face at all times.

I'm an ungrateful sod, I know..

Re:Visual Studio 2010 released by bad_user on Monday April 12, 2010 @02:21PM (#1259922)
Unfortunately it uses GTK. If you're on Windows try SharpDevelop.
Re:Visual Studio 2010 released by alexro on Monday April 12, 2010 @11:30AM (#1259341)
Why can't you remove all unnecessary components from the IDE? For me VS 2008 with Resharper makes no problems at all on my 4GB Ram desktop with loads of other crap running in parallel.
Re:Visual Studio 2010 released by rbanffy on Monday April 12, 2010 @11:34AM (#1259357)
Because "bloated" is still bloated, regardless of how much memory and processing speed you have at your disposal. It's much like a 200 Kg fat man driving a bus. He is still fat.

That said, I once thought Emacs was bloated. Now, it's quite nimble compared to other programming tools.

Re:Visual Studio 2010 released by gfodor on Monday April 12, 2010 @01:40PM (#1259809)
Stop anthropomorphising your computer. If your RAM, disk, and CPU let certain software perform as fast as necessary, any "bloat" you are asribing to things is purely psychological, philosophical, or due to something else like poor UI design. Traditionally, "bloat" means that there is too much memory-resident tools or features such that their cumulative effect, while negligable in separation, becomes daunting for your machine to handle, resulting in a sluggish user experience.

So, "bloat" is relative to your machine. What's "bloated" today is not going to be bloated 5-10 years from now, and vice versa. If this isn't what you're talking about, you're using the wrong word.

Re:Visual Studio 2010 released by rbanffy on Monday April 12, 2010 @08:03PM (#1260761)
> If your RAM, disk, and CPU let certain software perform as fast as necessary, any "bloat" you are asribing to things is purely psychological, philosophical, or due to something else like poor UI design.

Actually, bloat is measurable. It's the difference between being able to use a tiny netbook for a whole day without bothering to recharge it (provided you have a big enough battery pack) and having to be tethered to a desk for the whole day.

Of course I would love to have 16 cores of pure performance, 32 gigs of RAM, a couple terabytes of wicked fast SSD storage. Unfortunately, I wouldn't be able to fold it up, throw it in my shoulder bag and leave the office in order to work from a charming cafe while I watch the sunset. At least not for the next five years or so.

Everybody has priorities.

Re:Visual Studio 2010 released by anamax on Monday April 12, 2010 @12:12PM (#1259489)
> Because "bloated" is still bloated, regardless of how much memory and processing speed you have at your disposal. It's much like a 200 Kg fat man driving a bus. He is still fat.

While he's fat, it's not clear why it matters. (It matters to his health but not to the bus passengers.)

In what ways does the VS "bloat" matter?

Re:Visual Studio 2010 released by rbanffy on Monday April 12, 2010 @08:10PM (#1260789)
> In what ways does the VS "bloat" matter?

Basically, it will not run on a small netbook. Not at acceptable speeds.

http://news.ycombinator.com/item?id=1260761

Re:Visual Studio 2010 released by anamax on Monday April 12, 2010 @09:05PM (#1260896)
A lot of netbooks allow 2-3gb ram. Is that enough?
Re:Visual Studio 2010 released by rbanffy on Monday April 12, 2010 @09:15PM (#1260910)
It reduces memory time. Mine has 1.5 gigs. Never (well, almost never) touches swap. Disk is a bit slow, probably because low-rpm.

And it still runs Django faster than my company-issued 4 gig Windows Core 2 Duo laptop.

Re:Visual Studio 2010 released by rbanffy on Tuesday April 13, 2010 @06:13AM (#1261515)
Oops... "battery time". More momory reduces battery time.
Re:Visual Studio 2010 released by bad_user on Monday April 12, 2010 @12:02PM (#1259455)
A 200kg fat man can drive a bus just fine ;)

On Emacs ... you still have to pay attention to the loaded extensions, and if you've got dozens of them (especially the Jdee extension, with all the dependencies) it can be as bloated as a full IDE (and it shows in startup times).

Re:Visual Studio 2010 released by jefffoster on Monday April 12, 2010 @01:23PM (#1259765)
As a side note, you could run Emacs in daemon mode and connect to it with the client. See http://emacs-fu.blogspot.com/2009/02/emacs-daemon.html for more details. This way you only have to pay the startup cost once.
Re:Visual Studio 2010 released by rbanffy on Monday April 12, 2010 @08:08PM (#1260782)
Emacs runs comfortably on my netbook. I seriously doubt Visual Studio 2005 would be able to do it.
Re:Visual Studio 2010 released by jarek on Monday April 12, 2010 @11:07PM (#1261057)
I've ran VS 2008 on my almost-six-year-old laptop (P-M Banias 1.4 GHz, 1 GB DDR 333, 80 GB 5400 rpm) and I would not hesitate to call the experience "comfortable". What are the specs on your netbook -- is it really that much worse?
Re:Visual Studio 2010 released by alexro on Monday April 12, 2010 @11:31AM (#1259347)
I even start 2-3 copies of the IDE sometimes when doing work on several projects.

EDIT: wanted to ADD and didn't notice I was replying to myself

Re:Visual Studio 2010 released by rbanffy on Monday April 12, 2010 @11:34AM (#1259361)
You can always delete a post.
Re:Visual Studio 2010 released by csomar on Monday April 12, 2010 @12:40PM (#1259606)
It's fast enough in my 2.24Ghz Dual Core for Windows development.

For Asp.net, my sister went on a small project and I don't understand why the hell it does take lot of time to process pages.