| Whoever this guy is he's probably right. There are some really cool things coming forward in the land of dotnet.core. Specifically you can now build projects on linux machines. Command line and web are basically a "no brainer" already (even with RC1 and RC-here-be-dragons). For anyone seriously considering linux desktop apps, the'll want to consider some sort of cross-plat gui library, but there are a number of threads discussing it over at the dotnet foundation and some of the suggestions there seem like real "contenders" http://forums.dotnetfoundation.org/t/cross-platform-wpf/421 http://forums.dotnetfoundation.org/t/cross-platform-gui/514 (for example this one looked neat)
http://www.noesisengine.com/ When you're looking at C# vs. Java, I wouldn't be surprised if you found the new openness of dotnetcore to chip away at some of the "base" of Java. Maybe you start to see C# as the goto choice for CompSci classes. Maybe the face-melting performance benchmarks http://web.ageofascent.com/asp-net-core-exeeds-1-15-million-... (1.15 million requests per second vs. ~150k in nodejs and vs. 50k in .NET46) will have an impact on people interested in lowering their server costs. We certainly saw NODEJS was adopted rapidly thanks to its performance in 2012 http://highscalability.com/blog/2012/10/4/linkedin-moved-fro... and paypal followed suit in 2013 http://highscalability.com/blog/2013/12/11/using-nodejs-payp... C# under dotnet core, when written correctly has the potential to lower latency, require fewer servers, and all sorts of fun stuff. Fewer servers means lower costs, while lower latency has proven to convert into more users or sales. Of course, this is all best-case, pollyanna & coming from a bit of a fanboy... so please take what I say with a tiny grain of salt, but I do think this is pretty exciting stuff. To be fair, I'm so excited about this stuff I'd kindof like for someone to take me down a peg and push a bunch of
counter points at me so I get a more balanced and realistic opinion (just be nice OK?). |