Linked by David Adams on Thu 16th Jun 2011 17:46 UTC
Permalink for comment 477576
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links



Member since:
2009-08-18
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.
It is a general point ... stop being a pedant. You knew what my point was ... this sort of arguing is pathetic.
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.
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.
How to twist a comment around ... this is just pathetic.
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.
Fair point ... you should always use the best tools for the job, rather than blindly stick to something because you happen to know.
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.
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