Yes but Microsoft will take years to implement it and it'll be buggy meanwhile and you'll have fun buying two or three visuals in a row till you get what you want 2 years after ratification, like they are doing/did with c++11.
Well, Microsoft is the one pushing for graphics here, so I expect them to be the first to implement and publish such a library, as they did with all the technologies they were interested in.
Something cross platform and possibly based on OpenGL is very weird coming from ms, since they are so dismissive of crossplatformness and GL.
First, this is not about MS, it's about the C++ standard. Second, the standard will not provide nor specify an implementation. It specify only interfaces, and sometime performance scale expectations. So whatever the technology inside such a library, that might not be OGL. You don't even care, frankly, as long as your same code works for all platform, which is the point of having a standard library.
Maybe they're looking for graphics API to drop and since they dropped GL on phones and dropped XNA they ran out of things to safely drop(and D3D is no-no to drop).
You're again mixing things, this is not about replacing OGL, read the linked message, this is about 2D graphics only and the point is to have something to rely on both for games and GUI implementations. Also, they open the possibility of 3D but don't want to talk about it until a 2D library is ready.
Can I join rant and say that the next VS already includes some C++14 features, even though we're lacking important C++11?
That's what I'm saying: Microsoft is pushing for this library so it might appear sooner than having the full C++14 implementation from them.
Now, it's really a big problem that Microsoft tools, the most used in the C++ world, is the most lacking, but at this point and time I think they are making as much effort as they can to fix the game. From the point they started with, frankly, it's almost a miracle they managed to get as much features as the VS2013 version is supposed to provide.
That being said, this is not about Microsoft, focusing on the point of the library/disussion would be saner than bashing one implementor.