Originally posted by MyUserName
View Post
Ask yourself the question, if I have hundreds if not thousands of developers working for me globally, do I go with a development framework I can tie people into and save significant sums on associated development toolsets, infrastructure and the like or do I attempt to roll my own where I'm not likely to be shafted by suppliers having asymmetric release schedules whereby interdependencies do not match up. An example of this would be with Microsoft SSIS under SQL Server 2008 only allowing development against an older version of the .Net Framework - one which I've been bitten by before.
Although I don't intend to get into a language/framework flame war, I just prefer developing with C# rather than Python full stop. However, I can't argue with the economics of why many companies would choose Python as a first class citizen.
For me the answer is simple, Microsoft should make the development toolset free and cross platform. They're already moving in that direction anyway but if they want to stem the tide of people dumping languages such as C# they need to act sooner rather than later to make a free version of Visual Studio Professional or above... yes, yes, yes, I know there's already Visual Studio Code available on the likes of OSX but it's really not the same.
Comment