131–140 of 196 posts
Earlier quoted context omitted.
Microsoft does not care about C99. C++ is the official systems programming language in Windows, as has been communicated several times. C89 is good enough for writing device drivers, the only place Microsoft still advises to use C instead of C++. As for C99 support it is not as if Microsoft would be the only one not supporting it. http://en.wikipedia.org/wiki/C99#Implementations To be honest I think C99 and C11 will…
Are you looking at the same table I am looking at? All major compilers except MSVC 'mostly' support C99...
Have you validated what 'mostly' means?
Let me tell you that each compiler manufacturer has a different dictionary to look up the meaning of 'mostly'.
If a standard is not 100% implemented across compilers, no one can be sure to use it if portability is a concern.
This is exactly like the time where most databases 'mostly' implemented the SQL '92 standard, and then the code had to be full with DB specific workarounds.
Developers beware: Visual C++ 11 cannot compile executables that work on Windows XP at all: https://connect.microsoft.com/VisualStudio/feedback/details/... C++ devs may want to skip this release and just go for Visual C++ 12 when it's out, since by then hopefully XP will be ignorable.
OMG that's insane. Well, our Windows builds may just have to move from 2005 to 2010 and plan to be stuck there for the forseeable future. I was hoping I could use a C++11 compiler for Windows development someday. But it's probably more likely that I'll stop developing for Windows before my company's customers stop running XP.
http://windows.microsoft.com/en-us/windows/products/lifecycl...
XP doesn't run IE9 either, and it came out ages ago. XP is old now.
Earlier quoted context omitted.
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.
I have not heard of a single VS instance taking over 4GB of RAM. The only time you'll get into trouble is with multiple VS instances - and there 40 bucks for another 4GB of RAM pay off instantly.
Earlier quoted context omitted.
OMG that's insane. Well, our Windows builds may just have to move from 2005 to 2010 and plan to be stuck there for the forseeable future. I was hoping I could use a C++11 compiler for Windows development someday. But it's probably more likely that I'll stop developing for Windows before my company's customers stop running XP.
It is not "insane", XP is three years past the end of official support and only two years until the end of extended support. It's two generations old and possibly three by the time this is released. http://windows.microsoft.com/en-us/windows/products/lifecycl... XP doesn't run IE9 either, and it came out ages ago. XP is old now.
I don't think I've ever met anyone who managed fewer than 25 servers who has ever looked that that calendar.
Earlier quoted context omitted.
The key was "try". Xcode is far from being focused on "consumers" and they are trying hard to make a kick-ass IDE. It could be a different definition of "kick-ass" from yours, that's fine. Anyway, I emphasize this again: it's not a question if the actual result is better or worse, it's a complex question because there are thousands of people to evaluate it. The question is why not to experiment more where you have mo…
>It's hard to experiment with a toolbar in Excel because millions of non-computer-geek users Excel is another of my favorite "Why did they do that?" examples. In my opinion, MS absolutely ruined Excel somewhere in the transition from Office 2003 to 2007. If you were a power user with Excel'03 you felt like a total idiot with Excel'07. And, this wasn't a matter of a few buttons here and there. The thing was almost utt…
So I'm perplex about the need of a VM to run Excel 03 and won't debate about the use of it to generate code as anyone have different habits for his workflow.
Tangentially related: even in the redesign they manage to represent the save action using a floppy disk of all things. I wonder whether that is ever going to change as people forget what floppys were or whether this will just be the canonical icon for save even far into the future when nobody will really know that the icon does indeed have its roots in a long forgotten real-world object.
Changing it would need more learning and cognitive efforts by users.
Earlier quoted context omitted.
VS2010 is just damn slow and falls over on me at least 2-3 times a day which is not acceptable. Non-aggressive suggestion: think you've got something screwy with your system, I've had VS Fall over on my 2-3 times in the last several years of heavy use. It doesn't have to be that unstable. Also, with an SSD and enough RAM, I don't feel like I'm ever waiting on VS anymore.
I'd second that. In the past five years (or at least since VS 2008), I can remember VS crashing on me maybe half a dozen times. That's with spending most of my time working on pretty large multi language projects. For context, I don't use any extensions other than (sometimes) ReSharper and Tortoise svn/git/hg.
The solution does have about 80,000 files though.
The bloat associated with VS is utterly unnecessary, I think it's an opportunity missed that VS hasn't been peeled right back to a glorified Notepad++ with the VS Gallery providing the mechanism to add / remove additional features from MS and from third parties.