Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
julkali20696yI had the same thoughts! My guess is that because .NET Core (a.k.a. cross platform C#) is fairly new so folks still need to adapt to it. Think about it.
Those who already use ASP.NET (ASP.NET Core is arguably the most interesting part of .NET Core) run it on Windows server so why bother switching. And those who use Linux, which could consider switching, usually don't have any C# experience (because they are used to developing for Linux).
As for my part, I love C# and I see huge potential in Core. I will try to spread it wherever I may go. -
The company I'm working for is delivering around 1/3 of projects with backend in NETCore on RHEL7.
I understand here devs are pretty happy with that.
I'm closing my project these days on a mix of Java8/Wildfly & Node.js, next one will be NETCore on linux for me too (and I hope a good NET backender will be staffed too because my knowledge of that framework is very limited) -
BashouT5746yMy company is essentially full stack C# all of our (at least in our team's) APIs and simple admin areas are written in ASP.NET Core where possible.
We do our best to avoid JS frameworks if it's unecessary and .NET Core works really well when used in the appropriate places -
It's still a small child.
It has the character of an enterprise system (high level of software architecture), but is far too volatile to act as one. When I last played with it, 1 year old documentation was no longer working, half of the stackoverflow questions that I've found listed "working" solutions that didn't work any more, because of internal refactoring.
Documentation is poor, in comparison to how ASP.NET MVC is documented.
Plus, I can't count the number of times when stuff didn't work as expected. libssl issues on Ubuntu 17.04 - 17.10, AND on Debian were the worst.
Package manager is going nowhere. Project management as well. From a nice JSON to a stupid XML .csproj. NuGet is documented virtually only for Visual Studio and Windows. Adding / updating projects is one of the first challenges.
It's just... amazing that after I've worked years on Linux, and in parallel on Windows with .NET, it took me far more time to get .NET Core working than writing actual code. -
The thing I see now is a comeback of PHP, in a new, revamped mode, with far more language features being added, and it being a lot better at performance. There's now fewer and fewer reasons not to do stuff on PHP.
Sure. .NET core is faster once it starts up and has the big advantages that you're writing an actual server program and not an interpreter for individual requests.
But the biggest advantage of scripting languages like Python and PHP is that they can be deployed much faster and with much fewer problems. -
Thanks all.
I could have chosen to write the app in anything that would run on a windows server, but I decided to stick with what I know, and what our other dev knows.
I actually like it, and haven’t experienced any major issues yet. -
LMagnus20576y.Net core is our primary choice for development. So if it can be done in .Net Core that's what we use. Mainly because we can deploy it anywhere and it's open source.
However as others mentioned it's still not mature enough for every scenario, particularly EF Core. So for those situations we use .Net Framework MVC or Node.js.
I think over the coming years it will become more and more popular so I'd say stick with it!
Does anyone know of any apps/companies that are using .Net core in production?
I’ve started a project at work which consists of a webapi written in dotnet core, a react spa for the front end and xunit for testing.
I’m just curious as there are loss of sites about things written in Rails, or django, but almost nothing about dotnet core.
random