koo9koo9

signalR really bridges the gaps here. it would be nice to see websocket transport build in to the lib (instead of the requirement to run it in win8 and .net 4.5), but then it's an awkward situation to create a separate websocket implementation here. nontheless, it's very a  cool lib.

I would say, assembly coders don't produce garbage. bottom line is like C64 said, Use the right tool for the job. no matter it's .net, c, c++, it's all about trade off. it's either maintainability, time to market, cost of ownership, ease of development, speed. just pick one and go with it. however the message is clear now, C++ /11 is coming back, .net will stay low key for a little while or move to retirement mode but then it all depends on how popular c11 will be. nonetheless, it will be quite a bit of learning curve for the .net generation to pick up/brush up c++ again.

c++ is back to the spotlight. interesting.but really, where is this going?

good stuff!

rock on!

one quick question, where would be a good place to change the mouse cursor?  viewmodel is not the place, but then where would it be?