On the other hand having a filter construct is way nicer than having to manage the two arrays on your own.
Or worse yet, when someone is trying to remove items from a list that is self resizing, it is very easy to make bugs (by not adjusting the counter in the for loop when one is removed).
I understand that we get in a mess with different compilers not supporting the standard with cross platform code so MSVC should be changed.
But with respect to binding RValues to LValue references, why is the MSVC way not the standard? At first glance the MSVC way appears way more intuitive.
For instance if I have code:
update_X(X());
I would expect to be able to refactor it to this safely:
{
X x;
update_X(x);
}
The big catch is assuming that the team is big enough to put all the features into a variety of native apps.
It is possible that for a small team given the choice of one great web app or splitting time between Windows/OSx/iPhone/Android that the web app is superior.
At its face this looks like a good idea, but given the hassle of injecting the new checksum in the base file for every change I doubt it will be done by anyone but the most security conscious companies.
For me, the small screen is not an issue, because I typically develop on as much screen as I can muster.
As far as the editor, there are some good attempts at code completion from other systems, but I have not found one nearly as good as Intellisense. That is coupled with the jump to definition and declaration.
Also, the integrated debugging and some of the edit and continue functionality is amazing.
Maybe I should have been clearer. In the past you were not allowed to run OS X server in a virtual machine on non-apple hardware because of licensing restrictions. They loosened this restriction so that you can run OS X server in a virtual machine on non-apple hardware. Those sources are irrelevant to that.
I was responding to "Meanwhile there is no amount of money Apple will accept from you to run a mac vm on non Mac hardware." And this is not true for OS X server.
I am not sure I see the advantage in taking a metaphor that is a little off but understandable and replacing it with one that is more accurate, but very few people understand.