Visual Studio '11' Announced
111–120 of 196 posts
Re: Visual Studio '11' Announced
#112Earlier quoted context omitted.
Does anyone really use "save" so infrequently that they have not memorized the keyboard shortcut? There's a reason no apps on OS X have save icons...
They mentioned they dumped the clipboard buttons because nobody uses them. I would guess the need with Visual Studio isn't so much "Save" but "Save All", which also updates various project files. (I don't know the Save All shortcut off the top of my head - I almost always use the toolbar button.)
Re: Visual Studio '11' Announced
#113Earlier quoted context omitted.
>My biggest issue with VS2010 is the amount of memory it consumes RAM is so cheap now that there is really no excuse for developers to skimp on it. I would rather hope that they work on improving the product in other areas than optimize it for 1GB. If there are leaks however, they need to be addressed.
VS2010 is still a 32-bit app. This puts a limit on just how much RAM it can use. I for one might be a little less alarmed by (though probably no more happy about) its carefree attitude if it were a 64-bit app.
Re: Visual Studio '11' Announced
#114Earlier quoted context omitted.
>My biggest issue with VS2010 is the amount of memory it consumes RAM is so cheap now that there is really no excuse for developers to skimp on it. I would rather hope that they work on improving the product in other areas than optimize it for 1GB. If there are leaks however, they need to be addressed.
VS2010 is still a 32-bit app. This puts a limit on just how much RAM it can use. I for one might be a little less alarmed by (though probably no more happy about) its carefree attitude if it were a 64-bit app.
Re: Visual Studio '11' Announced
#115Re: Visual Studio '11' Announced
#116Earlier quoted context omitted.
I'm afraid XP won't be ignorable for another 3 or 4 years at least.
Microsoft stops providing XP security patches in April 2014. Any organization that wants to use XP after that will need to pay Microsoft to maintain support. Any organization that continues to use XP without support is irresponsible.
Re: Visual Studio '11' Announced
#117Earlier quoted context omitted.
fast is a relative term. If we're talking about VS 2010, then it's fast versus building an IDE with ed on your own. Honestly, I think you should really just consider checking your attitude and your politics at the door because loving Microsoft and all that proprietary software is just so old-school. It's boring and nobody cares that you think free software is evil.
Right, except nothing that I said conveyed any sort of gushing "love" for Microsoft or proprietary versus any other software. Listing "it's proprietary" immediately before "it's slow" OTOH? Yeah, it's pretty telling where that comment is coming from. If you don't like it, why come out of your way to make a negative comment about it unless you're just being a hater?
Intellectual honesty cannot coexist alongside zealotry.
Re: Visual Studio '11' Announced
#118Since they're making such a big deal on the new styling; would anyone know the rationale they had for making VS2010 purple?
Frankly, I'm impressed. The constantly shifting Office look and feel seems motivated by the desire to create artificial distinctions between versions of a product that peaked in 2000, or earlier.
Re: Visual Studio '11' Announced
#119Earlier quoted context omitted.
XCode 4 may have been designed but it wasn't designed well. It has no mixed source/disassembly views. Hovering over the debug icons say that pressing control and clicking "step into" will step a single instruction. But this isn't a sticky setting, so if I press control and click "step into" twice, the first time will step an instruction and the second will perform a source line step. It also crashes. A lot. When doin…
The stability will get there eventually. Xcode 3 got a lot better over the years.
It's called integrity. And although XCode has it from a design sense, it doesn't appear to have it in the engineering department.
Re: Visual Studio '11' Announced
#120Earlier quoted context omitted.
I use Excel extensively for automated code generation. I'm not going to argue if this is a good thing or a bad thing to do, but even you have to agree that this is an extremely rare thing to do, and something that would be more or less impossible for Microsoft to anticipate you doing.
I will argue, as I don't know who the submitter is, or even what this site is. HackerNews I think? I just got here via a Twitter post. So I have nothing to lose. If you're using Excel for automated code generation, YOU'RE DOING IT WRONG Surely there are better tools out there for the task.