31–40 of 235 posts
It will be quite nice if this ends up yielding results for individual JavaScript frameworks some day.
C# and .NET get a bad rap for being created by Microsoft. But one thing that can't be ignored is how polished their development tools are. I absolutely love coding in Visual Studio.
It pains me if I am honest. Our CMS is built on .NET and it's like an uphill battle selling it as it's on IIS and it's .NET. I have played around with the idea of reworking it into an open source language and open source database but I would miss Visual Studio and the language a lot. I don't get all the hate?
http://visualstudiogallery.msdn.microsoft.com/0e53eaf6-b031-...
What a co-incidence! Fred Wilson posted on this very topic this morning. http://www.avc.com/a_vc/2014/02/inspired-by-github.html From his post: "I was at a hackathon up at Columbia University last weekend and one of the hacks was a development environment that automatically queried StackOverflow and GitHub as you are writing code so that you always have in front of you the answers to the questions you are most likely…
Earlier quoted context omitted.
It pains me if I am honest. Our CMS is built on .NET and it's like an uphill battle selling it as it's on IIS and it's .NET. I have played around with the idea of reworking it into an open source language and open source database but I would miss Visual Studio and the language a lot. I don't get all the hate?
It's not .NET, .NET is a fantastic framework. The problem here is you're not just selling IIS and .NET, you're trying to sell the entire Microsoft ecosystem. There are so many MS components that just don't work on the Open Source world. Microsoft makes most of its money with its business products, so it's not cheap. Some companies just simply don't want to pay the Microsoft premium.
C# and .NET get a bad rap for being created by Microsoft. But one thing that can't be ignored is how polished their development tools are. I absolutely love coding in Visual Studio.
But F# is so much better that I can't think of a single reason for choosing C# over it.
If for nothing else - it shows MSFT's commitment to the language, to the platform and to the framework.
No, it shows MSFT's commitment to future revenue and profit. If they were really committed to the language, they would open-source it.
If for nothing else - it shows MSFT's commitment to the language, to the platform and to the framework.
No, it shows MSFT's commitment to future revenue and profit. If they were really committed to the language, they would open-source it.
Earlier quoted context omitted.
I was a kid back then so I don't know the details of the story. Can you give me a primer?
s/10/20 http://en.wikipedia.org/wiki/United_States_v._Microsoft#Hist...
If for nothing else - it shows MSFT's commitment to the language, to the platform and to the framework.
No, it shows MSFT's commitment to future revenue and profit. If they were really committed to the language, they would open-source it.
Earlier quoted context omitted.
No, it shows MSFT's commitment to future revenue and profit. If they were really committed to the language, they would open-source it.
It's in no way in a worse place than, say, java. It would be nice if the CLR and Roslyn was open sourced, but I wouldn't make it a primary concern when choosing a platform for a project. The ecma standardization feels at least as important.