And there's definitely nobody can see the current state of their underlying technologies to know about their transitions https://github.com/StackExchange
So ... this all just sounds weird for a startup with a weird name?
F# is nice, but always felt like the ignored child whenever I've used it.
If you like F#, why not just reap all the functional benefits and write it in Haskell, or Rust which has (arguably) just as strong a functional influence (minus the syntax) as F# does, with the benefit of a stronger type system, and better performance, and these days, probably a bigger community than F# as well.
Mostly because of user experience. F# as .NET language has entire ecosystem of high quality libraries to pick from, good IDE support (not as good as Java/C#, but definitely better than Haskell) and smaller learning curve. It's also way more robust than Rust - meaning that you can make a working project with decent performance much quicker. I say that as both F# and Rust developer. IMO the language that covers similar area and may be more tempting to learn is Scala. But if you already know how to utilize .NET platform, then reusing that knowledge in F# is just easier.
I'm a big fan of C# and the .Net platform as well. Being able to mix C# code in a project is compelling. If C# had a strong native SSH(I'm aware of netssh, but something a bit more official/active) implementation, and a WinRM/Remoting implementation that wasn't hidden inside the Powershell project, I think there would be a .Net OSS tools explosion..
Same here, our latest greenfield project was done in .NET Framework 4.7.2 and for the looks of it, the next one might be .NET Framework 4.8.
There are plenty of enterprise stuff like SharePoint, Sitecore, GUI components based on commercial partners like Telerik and Component One, among many others that are still on an transition to Core.
And for those that already moved there, their stability is still at v1.0 level, better leave the "fun" to others.
Because .NET Core isn't fully compatible with .NET Framework, and there are lots of stuff which people are willing to spend money porting them.
In the consulting business "I rewrote X in Y" blog posts only happen when someone takes the time to budget the project, because there is someone doing the math of developer time x cost per hour.
Then .NET Framework has been Windows specific for 20 years, there are lots of .NET libraries that are thin wrappers over Windows APIs, or interact with COM/UWP.
Porting them to Core means just rewriting everything from scratch, and if they are to remain anyway Windows specific, there is no advantage other than stay on reboot treadmill that Microsoft has started with the UWP/.NET Core (now backing off with Reunion), so they just keep doing .NET Framework as usual.
That stuff is pretty optional in 2020. I'd argue a lot of it isn't even relevant anymore. Sure, some people will still want/need it, but if you just want to spin up an API .NET Core is good to go.
True. I guess a lot of RFPs requiring software of that nature have probably been largely dominated by the Java and .NET ecosystems for decades and your Nodejs, Python, Ruby, Go ecosystems don't have any compelling offerings or much interest from their community to work on that sort of software?
I feel like a lot of what I see online fits into either SaaS web apps, or well known open source projects / core infrastructure used in building large-scale, distributed systems.
I'm sure there's a lot more out there, but it doesn't seem to get talked about much. Hence, the comment. Meaning if you're interested in coming over to the .NET Core world fr a different background then the things that are missing from full .NET Framework probably aren't of any interest to you.
Thaxll, meant there are no large scale enterprise .net core applications out there. All the examples here are not really large scale and are not used by millions of concurrent users daily. Bing is not fully .net core. Why LinkedIn and Github are not written on .net?
Going out of beta in a few days: https://github.com/SolutionsDesign/HnD (and already in production). Customer support system. .NET core, asp.net core mvc.
It's 2020 I can't name a single server side known application built in net core.