[sergiotapia]

I agree with you completely man. I'm working on my senior thesis to wrap up my degree and I have to use the Microsoft stack to write a real-time web app.

I haven't use MS stack since MVC2, and now we're at MVC5. I'm looking over the new things and now there's this new stuff called OWIN and Katana. Wat?

Buzzwords galore: iterative, modular, lightweight. Ugh. It used to work fine and now I have to learn some new thingamajig again.

[X4]

Sorry, but you don't learn actually anything new there buddy (there is more). You're right that MS packs all the un-branded wisdom into products with custom API's, SDK's coming with 20 new buzzwords describing the improvements. Well, because people love good packages. For MS software there are the Rx extensions and F#, but I'm sure that you can live with just ReactJS too. However here is some short but good read: http://www.infoq.com/news/2013/08/reactive-programming-emerg...

But if you once learned what FRP is, what Software-Engineering means, OOP Patterns, Functional Programming, then you'll be set for at least half of your life man. Also Real-Time Applications for the Web are a big misconception, they can only be of use where you really really need hard-real time applications. Which is mostly not the case with web-apps. What you need is a reactive web application, but please don't eat the BS in the reactive-manifesto.org. It's not wrong, but not intended for engineers and comes packaged with just hot-air, that according to the writers is "useful" to communicate to managers. I digress, but reactive programming is the concept you would be better of focusing on instead of real-time, except you are having one of the rare cases that actually needs hard-real-time synchronization.

OT: Am I hell-banned or something? My submissions appear dead at arrival.

[sergiotapia]

How can you suggest reactive web if you don't know what I'm building?