12 ms·
> Granted, that's only 1 month eyeball observation vs 5 years but it seems to be consistent with my perception of how much (how little?) C#/ASP.NET is used in t
by oblio 10y ago
> Granted, that's only 1 month eyeball observation vs 5 years but it seems to be consistent with my perception of how much (how little?) C#/ASP.NET is used in the startup scene.
This might change as dotnet core gathers steam. Mono was not considered a solid base by most companies, especially when compared to Java, while dotnet core has the QA assurances Microsoft can provide.
Xamarin was also commercial and was quite expensive just 1 year ago.
It would be an interesting experiment to monitor "Who's hiring" 2-3 years from now, I'm betting on .NET climbing quite steadily.
- dragonwriter 10y ago> This might change as dotnet core gathers steam. It also might not. > Mono was not considered a solid base by most companies, especially when compared to Java, while dotnet core has the QA assurances Microsoft can provide. This is true, but .NET and Windows both had that before: if the QA assurances Microsoft can provide was important to startups, the fact that a third-party reimplementation of .NET wasn't viewed as a solid base wouldn't prevent .NET uptake among startups. Now, if the only thing holding startups back from .NET was lack of first-class support for non-Windows platforms, .NET core might cure that, but I don't think it is.
- oblio 10y ago> Now, if the only thing holding startups back from .NET was lack of first-class support for non-Windows platforms, .NET core might cure that, but I don't think it is. I really don't see many reasons why other things would be blockers for startups. dotnet core is fast, it's cross platform, free and open source, so you can use it with very cheap hosting, C# is quite a nice language and on top of that it's "familiar", programmers can get their head around it very easily, the ecosystem is not that rich for cross platform (yet), but it is evolving rapidly, the apps can be compiled to native code. I really don't see any major downside to dotnet core, once the ecosystem reaches critical mass, which should happen in ~1-2 years.
- dragonwriter 10y agoC# is an fine language (better than Java), but C# and Java both have more enterprise traction than anything else. C# on .NET doesn't seem to offer much to people whose first choice, if it was excluded for lack of cross-platform first-party support, was something other than Java on the JVM. If you were going to pick Go or Scala or Erlang or Ruby/Jruby or Python if .NET wasnt an option, I don't think you are going to jump on C# if the reason .NET was excluded are gone -- if you were going to pick Scala, maybe F# is attractive in that case, but it seems to me that for most languages that startups actually seem to choose, it's unlikely that .NET being available changes that choice to one of the .NET languages. I think that .NET going cross platform will give it some uptick in startup adoption, but I'm skeptical about it being a big one.