151–160 of 162 posts
If you need to justify upgrades I would recommend measuring build speed savings in teams - vs 2012 & vs 2013 build faster than 2010 in my findings.
Anecdote: for one C++ solution I work on (two projects, 300k SLOC) VS2008: 5 min VS2012: 15 min VS2013 Preview: 10 min I use VS2012 and I'm about to use VS2013 for .NET development, but our C++ project is stuck in VS2008.
Earlier quoted context omitted.
It's not necessarily "monkeys", but, disturbingly, Microsoft developer tools are becoming more and more oriented towards "wizard-and-designer-clickety-clickery" type development. There are a few exceptions to this rule (think EF Code-First), but that's a drop in the ocean.
Enterprise developer here. That wizard bullshit is 100% enterprise. It's horrible to use and only exists because most enterprisey programmers are too terrible to grasp more productive coding methods. Still 100x better than digging through 100 pages of abstruse Java docs about AbstractProxyBeanDAOFactoryProxy.GenerateAbstractProxyBeanDAOFactoryAccessor though.
Closer to this: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... than drag and drop, clickety-click.
This rant has been brewing for many years... Everything's been downhill since VS6. I'm only joking, but seriously, does anyone remember how lightning fast VS6 was? That was over 15 years ago with much slower computers. I guess application 'snappiness' has not been a priority for the Visual Studio decision makers. I've used VS since the late 90s (writing node.js in ST2 now) and honestly appreciate the hard work and co…
Chromium is an extreme case of this. When we started we wanted to live the VS way of life (IDE tools and the like), so we had a Chrome.sln and various projects. Eventually it became too much. It would take minutes to load the sln, and woe to you if you synced your source tree while msvs was open, as you'd receive a neverending slew of modal prompts asking you to reload each of hundreds of projects. I think we still h…
Earlier quoted context omitted.
Chromium is an extreme case of this. When we started we wanted to live the VS way of life (IDE tools and the like), so we had a Chrome.sln and various projects. Eventually it became too much. It would take minutes to load the sln, and woe to you if you synced your source tree while msvs was open, as you'd receive a neverending slew of modal prompts asking you to reload each of hundreds of projects. I think we still h…
Semi OT: what is ninja? Tried looking it up but couldn't come up with a meaningful result.
Is it available on DreamSpark yet? There's a link to DreamSpark on the download page, but it takes you to the RC, which has been out for a while.
There's no link to DreamSpark on the download page [1] [1] http://www.microsoft.com/visualstudio/eng#downloads
Earlier quoted context omitted.
~50. A lot of the projects were created in older versions of VS, which may or may not matter.
Cool. I see in another response to your post that someone mentions minute load times just to load up the solution file, something which I thankfully have not experienced just yet. Makes me wonder what's accounting for the varied performance? Probably some combination of project size, plugins, and machine specs, I reckon. If one mans (persons) 10 projects contain 100x the code that my 50 projects contain it would cert…
This rant has been brewing for many years... Everything's been downhill since VS6. I'm only joking, but seriously, does anyone remember how lightning fast VS6 was? That was over 15 years ago with much slower computers. I guess application 'snappiness' has not been a priority for the Visual Studio decision makers. I've used VS since the late 90s (writing node.js in ST2 now) and honestly appreciate the hard work and co…
I think you may have selective memory with regards to VS6 (understandable over 15 years). Having recently worked at a company that for silly reasons did not upgrade beyond VS6, it was not lightning fast, took several minutes to open, and crashed frequently even with smaller projects. Modern VS really needs to work on managing large projects- but this isn't something it ever had to begin with, and has certainly improv…
> Also, VS would block for me a lot, but that was probably due using too many plugins.
Yeah, that's where your problem is. I'd put good money on ReSharper being the problem, as it's slowed me down in the past. Uninstalled it and never had another problem. The only plugin I have now is VsVim (which I highly recommend for those who'd like vim bindings.)
I'd probably still be using some MSFT technologies if I could use a VSS-style IDE on OS X without virtualization (I tired MonoDevelop, but it just wan't the same). I didn't have issues with the speed of Visual Studio running on my beefed up MBPro, but the keybinding stuff was just too much to deal with.
Not to mention, having a ton of different runtime/hosting options is a pretty nice bonus for the OSS stack.
Also, for mostly web apps, I think Visual Studio is massive overkill (but I'll still watch their videos on features).
For now, I've settled happily using on cross-platform tools (PyCharm/WebStorm for a feature rich IDE and Sublime Text 2 for code editing, and VIm when tweaking stuff on the server). Should I ever go back to Windows (likely, because I want a Surface Pro 2), my tooling should carry over (though I'll have to go through some keybinding issues again).
Never again will I use products that are locked down to a single OS. Even the tools on my Mac (with the exception of Keynote) run on Windows and vice-versa.