Note that you switch between "devs" and "customer" there. I argue that the real problem is that for VS those demographics are different. Devs in "Microsoft shops" don't go out and decide on a complier, they use VS because that's all there is. And the decision to purchase that compiler is made for them by the suited management class who frankly don't care about C++11 support beyond what they see in a line item checklist.
But you're right, that clearly the "devs" have preferences. The problem with your mechanism is that they don't express them to you in customer service requests. They just job-hop to another environment, doing Javascript work, or Linux, or Ruby. And you never hear from them.
Basically, the way feedback works in this world is with feet, not bug reports. If you build it they will come. If you don't they will leave.
On Windows there are lots of compilers to choose from.
They read in magazines the new shiny IDE has better team support and integrates seamlessly with Exchange and the SharePoint intranet deployed last year.
But let's be realistic here. Most of those shops will never hire someone to write C++ code. In all likelihood, they are still porting VB3 apps to VB.net.
The last time I managed to do a full greenfield C++ project at work was around 2005.
The enterprise has moved away from it long time ago and incoherence talk of Microsoft about going native does not help.
If they are serious about that I would expect proper C++11 support and improve ngen to the point I could use it as a real native code compiler. Not dumb UI changes.
>Basically, the way feedback works in this world is with feet, not bug reports. If you build it they will come. If you don't they will leave.
Is there any quantifiable metric to measure this so called exodus beyond anecdotes and the ".NET is dying" posts on here?
If there was an IDE for .NET on par with VS, it will definitely see uptake regardless of suits.
But that's really not the point. The upstream discussion was much narrower, and focused specifically on C/C++ support, which frankly sucks in the windows world compared to the renaissance we're seeing in Unix with our dueling multi-architecture full-support C++11 implementations.
I'm not nearly expert enough to comment on how good or innovative the .NET support in VS is, but I'm perfectly willing to believe it's great.
Your reasoning is really faulty because you aren't accounting for overall growth in the industry. If the world Irish population increases by 20% does this mean that the Asian population shrunk? Of course not.
Consider that Tablet and Smartphone platforms are in addition to flat PC sales. http://www.guardian.co.uk/technology/2013/feb/01/tablets-cro...
http://www.wcu.edu/ceap/houghton/edelcompeduc/ch1/handhelds/...
Same goes for the world wide web in general. http://www.businessinsider.com/how-many-web-sites-are-are-th...
You can't say logically that because there are more rails sites there are less Microsoft ones.
C# is pretty popular here: http://langpop.corger.nl/
here as well:
http://www.tiobe.com/index.php/content/paperinfo/tpci/index....
And that doesn't count non-C# .net ecosystem languages.
Could there be an exodus? Sure, but your reasoning is just wrong here.
I use Visual Studio ship code to run in browsers every day.
That accounts for a lot of software out there.
And no, I don't like Visual Studio, but it's the best tool out there for the majority of the people I work with.
https://groups.google.com/forum/?fromgroups#!topic/mozilla.d...
There are still internal limits in the PE32 format which mean parts of the output as a whole will be limited to 2 GiB or so, regardless of the address space available to the linker.
I too have hit internal linker limits from time-to-time, but the span of computing history in which it makes sense to have a 64-bit linker building a load module output with 32-bit internal limits to run on 64-bit processors doesn't seem like the place to be in the great scheme of things. Just my personal observation.
What hits the 32-bit limit is the link-time code generation, which has to have the entire program's AST, plus all the profiling information, plus whatever other data structures it's using in memory all at once.
For my custom Qt5 build, I've disabled /LTCG only for QtWebkit (32/64bit debug/release) and was able to deal with this limitation (at some other cost I guess)
Mozilla has never struck me as the most... forward looking.
* Edit: oops, I corrected a typo where I wrote "32-bit build".
So what are their problems exactly? That they are building with VS 2005 (from what I saw in that thread) and MS isn't backporting changes to the 2005 toolset?
[0] http://msdn.microsoft.com/en-us/library/0zza0de8%28v=vs.100%...
(Mozilla is building with 2010 now.)
Also note that the problem still exists in VS2012, and in fact is even worse because the linker memory usage has gotten higher in general. Fortunately we now have a fairly good workaround (developed with help from Microsoft -- maybe some of the people in this thread?) that limits which files participate in PGO:
The following list describes the various versions of cl.exe (the Visual C++ compiler):
...
x64 on x86 (x64 cross-compiler) Allows you to create output files for x64. This version of cl.exe runs as a 32-bit process, native on an x86 machine and under WOW64 on a 64-bit Widows operating system.
This 32-bit linker is apparently LARGE_ADDRESS_AWARE, so running it on 64-bit windows gets them 4GB to play with (which they are apparently rapidly burning through.) What they need is a 64-bit linker to run on 64-bit windows that can produce 32-bit output.
OS Linker Output Mem
1 32 32 32 3GB
2 32 32 64 3GB
3 64 32 32 4GB
4 64 64 32 8TB
They use to be doing 1, now they are doing 3. They need to do 4, but apparently cannot. My understanding of this may be wrong, or they may be wrong, I don't know.I am baaarely familiar with Microsoft-world development.
No. "Customer complaints" are not a substitute for product design sense.
Any survey of your customers is inherently biased: Your customers, by definition, are people who were willing to buy the product. You're rarely going to discover your biggest problems by counting the number of customers who report them, because your biggest problems are the ones that make people unwilling to become your customers in the first place.
https://connect.microsoft.com/SQLServer/Feedback
I think devs don't complain because there's not much point.
It took me 9 months and 45 calls to support to get a relatively simple regression in IE9/ClickOnce fixed and all we got was a fucking registry fix that we now have to ship to 2000 clients.
Basically they broke ClickOnce in IE9 for launching via scripts due to the new download prompting stuff.
Neither the framework team or IE team wanted to take responsibility leaving my poor support rep to reverse engineer both products.
It is never an either-or. It is always a complex mix of what customers ask for, what the strategic priorities/market realities are.
Often the problem with these queries is that there are not enough devs complaining to MSFT. No PM/engg manager is going to ignore a bug/problem if it shows up high in customer requests.
On promotions - I think it's the reverse problem. People only get promoted for working on something that's perceived to be hard.