Re:Node.js SDK for Windows Azure on Github
by politician on Sunday December 11, 2011 @01:08AM
(#3339421)
As a .NET developer who is actively transitioning to these technologies myself, I applaud Steve & Co; nevertheless, I don't understand the strategy. I was hoping someone around here could explain why this is in their best interest.
Re:Node.js SDK for Windows Azure on Github
by planetjoe on Sunday December 11, 2011 @01:29AM
(#3339448)
MS is trying to push enterprises to move their datacenters to azure. To do this, they have to support a wide array of technologies such as java/memcached/ruby.
Re:Node.js SDK for Windows Azure on Github
by jondot on Sunday December 11, 2011 @06:03AM
(#3339838)
That's a great business strategy for them.
But then again, they abandoned IronRuby, which is very frustrating. (what is the state of IronPython?).
Sounds like two hands that aren't really in sync.
Re:Node.js SDK for Windows Azure on Github
by sirclueless on Sunday December 11, 2011 @06:19AM
(#3339856)
Microsoft employs 90,000 people. Do you honestly expect all of them to be in sync at all times?
Besides, supporting third-party technologies on Azure and reimplementing open-source programming languages on top of the .NET framework seem tenuously related at best. That's actually one of the advantages of having a corporate agenda in my mind: things that are unlikely to gain traction with developers can be cut with impunity. It prevents fracturing and slowing down communities, all too common in the open-source world (think of the many, many variants of Lisp, or the recent explosion of LanguageX-to-javascript compilers).
Then there are also other articles on consuming Azure services with clients written in many languages. http://blog.smarx.com/posts/windows-azure-storage-libraries-...