An API is like a platform or a mini-platform. 5,000 of them makes no sense. Do they mean 5,000 new API function calls in the Windows platform or something? Although that would be insanely large too. I don't get it.
»In that context, we have our Build 2013 developer conference this week in San Francisco, where approximately 5000 developers have gathered in person (with many thousands more watching virtually) from around the world to discuss the next generation of software development with platforms and tools from Microsoft.«
Maybe someone just confused developers and APIs...
I was worried for a minute there.
I don't know any product that could even reach 5000 API calls. Win32 isn't anywhere near that even after 20+ years.
More likely they're just sloppily enumerating function endpoints.
I think Apple meant new methods, classes and possibly even the options that you could pass as arguments.
Whatever it means I don't think that more is necessarily better and I hope no one has adding APIs as a performance metric!
> "Lion offers over 3,000 new APIs covering a range of new technologies and capabilities."
A single function call specification is an API; and the union of two APIs is an API. So it's perfectly cromulent to say "We added 5000 new APIs to the WinRT API", as bizarre and confusing as it sounds, though AIUI only Microsoft routinely refers to single function signatures as APIs -- perhaps to make their products sound more impressive.
'Managed return value inspection' is a nice enhancement too.
With Visual Studio 2013 Preview, you can now use [Edit and Continue] with x64,
AnyCPU, and (of course) x86 projects.
Expanding the API, at least in that direction, is probably a great thing.
I'm not complaining as I get it on MSDN under my subscription.
Yesterday i had to explain to some people i work with what Microsoft is, they dont know it, and dont understand it, they are used to android these days. And find the whole thing confusing why pay for it ?.. its hard to justify or explain..