Linked by David Adams on Thu 16th Jun 2011 17:46 UTC
Games Microsoft has released a beta SDK for Windows, allowing Windows developers to officially make use of the XBox Kinect hardware. From their own press release: "The Kinect for Windows SDK, which works with Windows 7, includes drivers, rich APIs for Raw Sensor Streams, natural user interfaces, installer documents and resource materials. The SDK provides Kinect capabilities to developers building applications with C++, C# or Visual Basic using Microsoft Visual Studio 2010."
Permalink for comment 477576
To read all comments associated with this story, please click here.
RE[5]: Comment by Kroc
by lucas_maximus on Fri 17th Jun 2011 18:05 UTC in reply to "RE[4]: Comment by Kroc"
Member since:

I think you've missed the point of my post by quite a margin.

No I don't think I did. I think you are making an argument because you think there is something inheritantly wrong with developing with Visual Studio.

...because this topic is about software development...

It is a general point ... stop being a pedant. You knew what my point was ... this sort of arguing is pathetic.

Well yes. But we're talking specifically about developers so i didn't see the point in discussing other industries.

I wasn't discussing other industries. I was discussing software development. I actually work somewhere where there has been no code quality enforced (code reviews, naming conventions etc etc) ... I spend most of my day rewriting legacy code. How software development is managed is probably as important as the talent and knowledge of the developers themselves ... if not more so.

Because if you are lazy and you've learned how to use this SDK, then why would you bother learning how to use another SDK. This is particularly true for hobbyists.

Why would you bother using another SDK when you already know how to use the current one? It is laziness ... it is being sensible. I have some javascript code running on a website of dubious quality (written when I was far more inexperienced), but I left it as is .. because it works fine.

Well clearly you're not lazy so your anecdotal evidence is irrelevant

How to twist a comment around ... this is just pathetic.

I agree, *if* you're a good programmer. However we're discussing the other end of the spectrum.

Which is entirely my point in the first place ... if people happen to learn with Microsoft tools but understand the principles they will still be able to transition to whatever ... if they don't bother to learn the principles they will be starting from square one again ... however that doesn't mean that it is bad for Microsoft to release a SDK.

Not everybody falls into the category you're describing. There's a massive number of developers and hobbyists that will just make do with whatever tools and languages they're already familiar with. In fact, most developers (even the good ones) will favor a project in a language they're already experienced in than want to learn a new language just for the sake of learning a new language.

Fair point ... you should always use the best tools for the job, rather than blindly stick to something because you happen to know.

So while this move by MS isn't a "lock in" in the traditional technical sense of the term, it does give users more reason to stick with VS / .NET rather than learn open source tools.

1) Microsoft have no responsibility to help third party projects.

2) Why shouldn't users learn how to develop with Microsoft Tools? ... There is a lot of jobs out there for devs that know how to develop using Microsoft tools .. are you saying that people shouldn't make themselves employable?

3) If open source tools are to be more widely used then they have to be more attractive to use than the (Microsoft in this case) alternatives.

To put an analogy on this: it's like how Linux users moan about who many students are taught how to use MS Office, not generic office tools. Thus users are naturally more drawn toward MS Office as it's what they're familiar with despite the fact that general office computing skills are easily transferable between all the big office software suites.

In terms of using IDEs, I have to agree. I don't know my way around Eclipse as well as I used to.

Edited 2011-06-17 18:07 UTC

Reply Parent Score: 2