This is awesome.
> I think this is an important message for several reasons:
>
> * First time a Microsoft exec has addressed the community by name in an
> official communication (note OpenKinect in the tags).
> * First time Microsoft has used hacker in our preferred form in the positive
> connotation when referring to our efforts.
> * Admits that they didn't have all this planned out in advance and properly
> credits our communities and efforts as the reason why Kinect for Windows
> product even exists
> * Clarifies that the primary goal of the commercial program and new hardware
> is to provide a way for businesses to use officially supported hardware on
> Windows. (Its no longer just a toy in the eyes of traditional business
> decision makers, which should help everyone get more things done in more
> places, even with OSS drivers.)
> * Further clarifies that the K4W v1 SDK will continue to support existing
> Kinect for Xbox 360 sensors so that the community can keep using them as we
> have been.
Hooray!
> While they didn't say it this bluntly, i think the message here is that if
> official support and/or the new features (with more to come) are important
> to you, such as if you are a business, get the new K4W sensor. If not, keep
> using the Kinect for Xbox sensor. (Not legal advice and I haven't seen any
> final license yet.)
True, but promising nonetheless.
> Also notable that there has still been no attempt or even implication that
> they are trying to lock out the existing open source drivers, whether
> libfreenect or OpenNI. Instead, they are trying to legitimately compete on a
> technical excellence level by creating a great SDK, even though they could
> easily go the legal route instead. There is most definitely room for
> multiple drivers and SDKs and competition helps drive innovation. We drove
> them to innovate even more!
This is fantastic. I am so happy to see Microsoft making a public
statement to this effect. Much of the OSS world puts forth their
efforts expecting no reward but acknowledgement that they have created
something worthwhile. Our efforts have become an international
inspiration, and I'm proud to be a member of this community.
So in the same thread: thanks to all you folks for building the
impressive, creative showcase of what a hacker community can do!
> I think there are still ways Microsoft can work with the community better
> (OS X & Linux support, open sourcing components of the SDK, joint
> Microsoft-community development efforts) however I think this communication
> is a big step in the right direction. This message was in direct response to
> our feedback both in the other OpenKinect thread and elsewhere on the web.
Agreed.
> Thanks,
> Joshua Blake
> OpenKinect Community Founder
>
> P.S. That first picture in the blog is of me from the Kinect SDK beta launch
> event.
Best,
Drew Fisher
i wonder if 'hacker' has ever been used in a positive sense by
microsoft before? that in itself is a huge step. i like that they tag
on "and enthusiasts", just to make sure no one gets confused :)
> trying to legitimately compete on a technical excellence level by creating a great SDK
this is definitely preferred to 'the legal route'. but something i'm
still confused about is why they need to compete at all? i feel like
if they were more open, the hacker community would start doing the
work of things like osx and linux porting. and as stated in a previous
message to this list, i would also expect libfreenect to borrow
windows improvements, the same way the libfreenect registration code
was borrowed from openni.
microsoft is like that one really socially awkward friend. generally
well intentioned, but sometimes they just don't understand the
dynamics of social space.
for example, i can imagine that "the kinect effect" campaign was
supposed to come off as "good job hackers! you amazed us!" but it
ended up feeling a little more like "well of course you're innovating
with microsoft products. we will now associate ourselves with your
movement and reap the fuzzy warm feelings." the only solution is for
everyone to continue doing what they do best, and over time microsoft
will find that the best way to work with the open source community is
on their own (our own) terms. i'm dreaming of a symbiotic
relationship, between a huge company with enough money to create
democratically priced hardware, and millions of people who innovate
with software because they love to... but it will take time.
kyle
This was just posted on the Kinect for Windows blog. It is essentially a thank you note from Craig Eisler, General Manager of K4W to all of us for our visionary efforts with Kinect and helping teach Microsoft what can be done with the sensor.
http://blogs.msdn.com/b/kinectforwindows/archive/2012/01/12/the-power-of-enthusiasm.aspx
I think this is an important message for several reasons:
* First time a Microsoft exec has addressed the community by name in an official communication (note OpenKinect in the tags).
* First time Microsoft has used hacker in our preferred form in the positive connotation when referring to our efforts.
* Admits that they didn't have all this planned out in advance and properly credits our communities and efforts as the reason why Kinect for Windows product even exists
* Clarifies that the primary goal of the commercial program and new hardware is to provide a way for businesses to use officially supported hardware on Windows. (Its no longer just a toy in the eyes of traditional business decision makers, which should help everyone get more things done in more places, even with OSS drivers.)
* Further clarifies that the K4W v1 SDK will continue to support existing Kinect for Xbox 360 sensors so that the community can keep using them as we have been.
While they didn't say it this bluntly, i think the message here is that if official support and/or the new features (with more to come) are important to you, such as if you are a business, get the new K4W sensor. If not, keep using the Kinect for Xbox sensor. (Not legal advice and I haven't seen any final license yet.)
Also notable that there has still been no attempt or even implication that they are trying to lock out the existing open source drivers, whether libfreenect or OpenNI. Instead, they are trying to legitimately compete on a technical excellence level by creating a great SDK, even though they could easily go the legal route instead. There is most definitely room for multiple drivers and SDKs and competition helps drive innovation. We drove them to innovate even more!
I think there are still ways Microsoft can work with the community better (OS X & Linux support, open sourcing components of the SDK, joint Microsoft-community development efforts) however I think this communication is a big step in the right direction. This message was in direct response to our feedback both in the other OpenKinect thread and elsewhere on the web.
Thanks,
Joshua Blake
OpenKinect Community Founder
P.S. That first picture in the blog is of me from the Kinect SDK beta launch event.
+1
It is though great news now, and I hope the word stays... but I think
majority of us know how "big shots" at M$ change colors, words, and
what not. Today they are hugging us, tomorrow?
Only time can tell.
For now we can celebrate (but not let guard down) :)
Btw, anyone got a piece of the K4W hardware in here?
--
Krish
www.toonheart.com