MS Embraces Elephant of Open Source (Hadoop)(wired.com)
wired.com
MS Embraces Elephant of Open Source (Hadoop)
http://www.wired.com/wiredenterprise/2011/10/microsoft-and-hadoop/
5 comments
Probably has something to do with this:
"Sun Microsystems, the creator of Java, sued Microsoft in October 1997 for incompletely implementing the Java 1.1 standard.[2] It was also named in the United States v. Microsoft antitrust civil actions, as an implementation of Microsoft's Embrace, extend and extinguish strategy. In 2001, Microsoft settled the lawsuit with Sun and discontinued its Java implementation"
Glad to see they're acting more mature these days.
"Sun Microsystems, the creator of Java, sued Microsoft in October 1997 for incompletely implementing the Java 1.1 standard.[2] It was also named in the United States v. Microsoft antitrust civil actions, as an implementation of Microsoft's Embrace, extend and extinguish strategy. In 2001, Microsoft settled the lawsuit with Sun and discontinued its Java implementation"
Glad to see they're acting more mature these days.
> Glad to see they're acting more mature these days.
They still intend to port Hadoop to Windows. There is little to prevent extending it.
They still intend to port Hadoop to Windows. There is little to prevent extending it.
And I'm sure they will. . . but lately Microsoft seems to have grown up and learned to not create incompatible extensions. Perhaps they're finally starting to realize that nobody really loves them, so if they refuse to be nice to other children then they'll just get kicked out of the schoolyard. (Ballmer and upper management may not have, but they're facing the real possibility of a mutiny right now.) So it'll hopefully just end up being the kind of situation where if you switch platforms you'll lose some of the bells and whistles that were provided in a library on the old platform. Just like what would happen if you switch from one open-source platform to another.
What concerns me more is:
> the company is providing “connectors” for moving data between the two.
Microsoft loves to sink a lot of time into gee-whiz crap that lets their MVCs throw together gee-whiz crap using GUI tools without ever writing any code. They love it so much that they often waste all their effort on that stuff without bothering to get the fundamentals in order, and the end result is unusable garbage like much of ADO.NET and early versions of Entity Framework. That one sentence makes me fear more of the same old garbage: We'll get a port of Hadoop that comes with a plethora of toys in the System.DraggyDroppy namespace for impressing the suits, but is crippled by a broken set of bridge libraries for the programmers.
Which is fine. A Windows port of Hadoop isn't really necessary. We can just keep using REST or whatever to keep the Windows servers talking to the servers that do actual work, and Microsoft can keep chasing its own tail while it slides into irrelevance, and everyone can be happy.
What concerns me more is:
> the company is providing “connectors” for moving data between the two.
Microsoft loves to sink a lot of time into gee-whiz crap that lets their MVCs throw together gee-whiz crap using GUI tools without ever writing any code. They love it so much that they often waste all their effort on that stuff without bothering to get the fundamentals in order, and the end result is unusable garbage like much of ADO.NET and early versions of Entity Framework. That one sentence makes me fear more of the same old garbage: We'll get a port of Hadoop that comes with a plethora of toys in the System.DraggyDroppy namespace for impressing the suits, but is crippled by a broken set of bridge libraries for the programmers.
Which is fine. A Windows port of Hadoop isn't really necessary. We can just keep using REST or whatever to keep the Windows servers talking to the servers that do actual work, and Microsoft can keep chasing its own tail while it slides into irrelevance, and everyone can be happy.
> We'll get a port of Hadoop that comes with a plethora of toys in the System.DraggyDroppy namespace for impressing the suits
Sadly, for programmers who work where the impressionable suits reign, it's usually the suits who pick the tools their underlings will have to use to assemble whatever was conceived in the demos. They'll end up having to deploy Hadoop on Windows 8 Server and talk to it using the vile offspring of Clippy and Hadoop that lives under System.DraggyDroppy.
Sadly, for programmers who work where the impressionable suits reign, it's usually the suits who pick the tools their underlings will have to use to assemble whatever was conceived in the demos. They'll end up having to deploy Hadoop on Windows 8 Server and talk to it using the vile offspring of Clippy and Hadoop that lives under System.DraggyDroppy.
And yet the suits wonder why there is such a shortage of competent developers who are willing to work in .NET.
A lot of things can be utterly incomprehensible to the suits. We have to be patient with them.
> Perhaps they're finally starting to realize that nobody really loves them, so if they refuse to be nice to other children then they'll just get kicked out of the schoolyard.
I for one love Microsoft. There, I said it.
I for one love Microsoft. There, I said it.
"But it was all right, everything was all right, the struggle was finished. He had won the victory over himself. He loved Big Brother."
(Disclaimer: I work for Microsoft.)
(Disclaimer: I work for Microsoft.)
> (Disclaimer: I work for Microsoft.)
It's OK. It's not your fault.
It's OK. It's not your fault.
I'm confused, if Hadoop is Java, what is there to port? Won't it just run as-is on Windows (Azure supports Java already)
Have you ever seen an application in Java that actually works in more than one system without any env-specific code at all and does not behave in a slightly incompatible way? I haven't. (apart from toy apps which exist only to prove the opposite)
Fair enough. I did just read this - "Various parts of Hadoop are executed using shell scripts that will only work on a Linux shell.". Sounds like you need Cygwin (currently). Guess those are the bits that will be ported.
> apart from toy apps which exist only to prove the opposite
They also prove it's possible to write portable code in Java. ;-)
They also prove it's possible to write portable code in Java. ;-)
The same logic says that it is possible to write portable C programs. ;)
That's nothing! It's even possible to write portable C# programs. Now that's an accomplishment. ;-)
Probably the main thing is creating a .NET library for talking to Hadoop.
I don't think Azure needs to run Java to succeed, but it certainly wouldn't hurt. And they've been pretty out-front with supporting Java for a while:
* Open source SDK for Java (and Eclipse): http://www.windowsazure4j.org/ * Gigaspace running their products on Azure: http://www.gigaspaces.com * More info (admittedly from a UK-based Azure consultant): http://www.theregister.co.uk/2011/09/09/java_on_windows_azur...
To me, this sounds like a pragmatic continuation of their 'big data' plans on Azure -- gotta go after what the current user base is used to using -- and probably compliments their own Dryad project (http://research.microsoft.com/en-us/projects/dryad/)
* Open source SDK for Java (and Eclipse): http://www.windowsazure4j.org/ * Gigaspace running their products on Azure: http://www.gigaspaces.com * More info (admittedly from a UK-based Azure consultant): http://www.theregister.co.uk/2011/09/09/java_on_windows_azur...
To me, this sounds like a pragmatic continuation of their 'big data' plans on Azure -- gotta go after what the current user base is used to using -- and probably compliments their own Dryad project (http://research.microsoft.com/en-us/projects/dryad/)
The company is now working to port the Hadoop platform to Windows — it was built for use atop Linux — and Doug Leland, general manager of product management for SQL Server, told Wired that the company plans to eventually release its work back to the open source community.
Haha, some things never change. A code dump of major changes developed in isolation. I'm sure the Hadoop commuity will love that.
Haha, some things never change. A code dump of major changes developed in isolation. I'm sure the Hadoop commuity will love that.
I m still waiting for the microsoft linux distro.
That is officially called suse http://blogs.computerworld.com/17416/who_really_bought_novel...
if you want to buy "protection"
It's really great to see Microsoft moving on to embracing change, first WP7 and now this. A tendency and a positive attitude towards evolving the company is noticable.
but what about dryad?
It seems like Microsoft has had a policy of not touching Java with a ten foot pole for some time now. At least, since .NET came out, they've been pretty proactively anti-Java.