News for hackers. Stuff that matters.
Re:Visual Studio 2013 by jblow on Monday June 03, 2013 @03:06PM (#5815162)
Yet another Visual Studio, yet another truckload of "features" that do nothing to help day-to-day, heavy-lifting programmers. (And which probably help by adding bugs or just bloating the system). Sigh.

I am hoping they have made substantial improvements that are not mentioned in this blog post.

Re:Visual Studio 2013 by kvb on Monday June 03, 2013 @03:49PM (#5815463)
Note that the blog author is part of the Team Foundation Server organization, so it's natural that he's talking about those features and not the programming language and runtime features.
Re:Visual Studio 2013 by jblow on Monday June 03, 2013 @03:09PM (#5815189)
... though I guess if you look at the rationale behind all these features as "get people who buy into these features so tangled up in them that they can't use anything else, or reasonably port their applications to another OS", then it all makes sense.

Of course, that is the opposite of what I as a software developer want.

Re:Visual Studio 2013 by Permit on Monday June 03, 2013 @03:42PM (#5815428)
Out of curiosity, what kind of improvements would you like to see in Visual Studio?
Re:Visual Studio 2013 by kabdib on Monday June 03, 2013 @05:52PM (#5816280)
Server farm builds.

A keyboard macro system that doesn't suck (e.g., is available and /as fast/ as the one in Emacs).

A way to compare project configurations without involving either XML or a sea of random dialog-like boxes.

The TFS and workflow features they are adding make me weep.

Re:Visual Studio 2013 by jussij on Monday June 03, 2013 @07:34PM (#5816810)
> A keyboard macro system that doesn't suck (e.g., is available and /as fast/ as the one in Emacs).

FWIW the Zeus IDE has keyboard macros that can be recorded/written in Python, Lua, Javascript or VB Script and it can even import VS woskpaces.

Re:Visual Studio 2013 by kabdib on Monday June 03, 2013 @10:22PM (#5817313)
Yeah. But.

The VS keyboard macro system has "overengineered" written all over it. Really all they had to do was record some keystrokes. Instead they probably had a team of like four engineers, a bunch of Q/A and several PMs on it, and it took them over a year. And the result /stinks/; it blows dead exploding goats.

Sigh.

Re:Visual Studio 2013 by sixothree on Monday June 03, 2013 @06:30PM (#5816498)
I really just wish they improve the darn search feature. It's just lowsy for pretty much anything but a small project.
Re:Visual Studio 2013 by ksk on Tuesday June 04, 2013 @07:25AM (#5818743)
Those features are actually designed for their marketing team, not developers. :P
Re:Visual Studio 2013 by gokhan on Monday June 03, 2013 @04:21PM (#5815684)
Try R# with VS.
Re:Visual Studio 2013 by pointyhats on Monday June 03, 2013 @04:40PM (#5815844)
Try R# with VS in a solution with 54 projects and ~ 1.5MLOC...

It stinks!

Re:Visual Studio 2013 by trust-me on Monday June 03, 2013 @07:16PM (#5816728)
Are you serious? That's a medium size project, just get a fast machine (e.g. i7 4770) and you'll be perfectly fine.
Re:Visual Studio 2013 by pointyhats on Tuesday June 04, 2013 @01:20AM (#5817864)
I've got an 8 core 3.0 Xeon with 32Gb RAM and Samsung 840. It's still slow.

It's more latency than long waits but it's enough to stop me using it.

Re:Visual Studio 2013 by trust-me on Wednesday June 05, 2013 @03:39PM (#5828069)
8 core Xeon would be good at video rendering, but as of now for VS and R# you need single threaded performance, where a 3.9GHz Haswell shines.
Re:Visual Studio 2013 by wluu on Monday June 03, 2013 @06:46PM (#5816585)
Well, I don't know how many LOC I have, but I'm sure close to or more than that.

But we've got 62 projects. I've turned off a few things like code analysis in R# and it runs fairly well.

Re:Visual Studio 2013 by manojlds on Tuesday June 04, 2013 @12:02AM (#5817641)
But the point is, we have to buy the costly VS AND pay a third party to get the real goodness of an IDE.