Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Visual Studio 2013

blogs.msdn.com

Post reply on HN
Print view View original

21–30 of 201 posts

Re: Visual Studio 2013

#21

Post by evo_9 »

MartinCron wrote: post #14
evo_9 wrote: post #8

Way way way way, WAY too soon Microsoft... most shops, including my current employer aren't even on 2012 yet... Honestly I prefer VS to be tied to desktop OS releases or SQL release or something other than yearly. This is not a Madden game, nobody is asking for yearly updates for Visual Studio.

nobody is asking for yearly updates for Visual Studio Ahem... I am. I would much rather have smaller more frequent updates to important tools than huge disruptive ones. Short feedback loops are a good thing.

Full new version or Service Packs?

I agree with you but a Service Pack should suffice esp. right after you've release a full new version/update to a major product/tool like VS.

Re: Visual Studio 2013

#22

Post by CoolGuySteve »

I wish they would dedicate more time to improving cl.exe and link.exe in terms of performance and language support and less time with these hokey team visualization gimics.

Every release since 2008 has been getting slower and slower for C++, the C compiler is awful, PGO instrumentation in Win8 is less capable, and there's no equivalents in the Windows ecosystem to gcc's likely/unlikely, oprofile, or valgrind.

It's at the point now where developing on Windows vs Linux is a serious performance and security impediment due to their withering native toolchain. But I guess nobody over there gets promoted for fixing the hard stuff.

Re: Visual Studio 2013

#23

Post by Gazk »

evo_9 wrote: post #8

Way way way way, WAY too soon Microsoft... most shops, including my current employer aren't even on 2012 yet... Honestly I prefer VS to be tied to desktop OS releases or SQL release or something other than yearly. This is not a Madden game, nobody is asking for yearly updates for Visual Studio.

There is a new SQL release, SQL Server 14.

Re: Visual Studio 2013

#24

Post by jlewicki »

GravityWell wrote: post #13
r4vik wrote: post #3

Earlier quoted context omitted.

menu still shouting

I personally don't mind the menu caps, but I do find the way they are forcing their design choices on everyone somewhat antagonistic, and generally not smart. The same issue happened with their forced grey or white color schemes. It's not hard to give users the option to switch things like this to suit their preference. Yet MS has deliberately not provided any way to adjust these settings, and this gives users someth…

You can indeed edit the color scheme.

http://visualstudiogallery.msdn.microsoft.com/366ad100-0003-...

Re: Visual Studio 2013

#26

Post by darkchasma »

CoolGuySteve wrote: post #22

I wish they would dedicate more time to improving cl.exe and link.exe in terms of performance and language support and less time with these hokey team visualization gimics. Every release since 2008 has been getting slower and slower for C++, the C compiler is awful, PGO instrumentation in Win8 is less capable, and there's no equivalents in the Windows ecosystem to gcc's likely/unlikely, oprofile, or valgrind. It's at…

"hokey team visualization gimics" keep management off the teams ass, so I appreciate a little attention. Though I ultimately agree, there isn't a lot here that's scratching any of our itches.

Re: Visual Studio 2013

#27

Post by Luyt »

r4vik wrote: post #3
chiph wrote: post #2

That was fast.

menu still shouting

This pisses me off, too. I really should patch the menu resource someday and change it to lowercase. I also don't understand that Microsoft violates its own HID guidelines; shouldn't they set a proper example?

Re: Visual Studio 2013

#28

Post by Silhouette »

samirahmed wrote: post #16
evo_9 wrote: post #8

Way way way way, WAY too soon Microsoft... most shops, including my current employer aren't even on 2012 yet... Honestly I prefer VS to be tied to desktop OS releases or SQL release or something other than yearly. This is not a Madden game, nobody is asking for yearly updates for Visual Studio.

I find this response almost shocking. Most of HN criticizes microsoft for slow releases cycles, slow change but the Visual Studio has clearly made progress for the better by addressing UserVoice requests, integrating Git etc. If your employer is to slow to keep updated, why should that slow MSFT down for you while the it is trying to reinvent itself, just catch up in 2015.

Most of HN criticizes microsoft for slow releases cycles

Just because it's trendy to bash MS for not releasing new browsers/IDEs/whatever every few weeks, that doesn't mean the vocal critics speak for all of us, nor even necessarily for the majority. I get paid to build stuff that works, and doing so requires stable foundations and reliable tools. Lately, I wish we had more Microsofts in the world paying attention to things like backward compatibility and long-term support, and fewer Googles and Mozillas and Apples who are quite happy to push out updates that break useful things that worked before.

There was nothing wrong with releasing a major version when you had major new features, more frequent minor versions that introduced minor features in a compatible way, and point releases for urgent security issues or bug fixes that didn't change any intended behaviour at all. This approach has worked for a long time, and IMNSHO the recent regular, fixed schedules for updates regardless of actual changes aren't doing most people any favours, and the version-free, always-online, push-updates-whenever stuff is just a mess that causes far more trouble than it's worth.

Re: Visual Studio 2013

#29

Post by TylerE »

CoolGuySteve wrote: post #22

I wish they would dedicate more time to improving cl.exe and link.exe in terms of performance and language support and less time with these hokey team visualization gimics. Every release since 2008 has been getting slower and slower for C++, the C compiler is awful, PGO instrumentation in Win8 is less capable, and there's no equivalents in the Windows ecosystem to gcc's likely/unlikely, oprofile, or valgrind. It's at…

How hard would it be to create stub apps that really just call out to clang/llvm?

Re: Visual Studio 2013

#30

Post by whaevr »

mischanix wrote: post #7
r4vik wrote: post #3

Earlier quoted context omitted.

menu still shouting

I don't mind it. It's not like it's high-contrast, large font, or bold, it just serves as a heading for the menus they show without making the font large or bold. It's definitely nowhere near as annoying as intellisense randomly breaking and putting a red line underneath half your statements.

>It's definitely nowhere near as annoying as intellisense randomly breaking and putting a red line underneath half your statements.

I feel your paIEnumerable

Post reply on HN