3 ms·

Don't discount C# and the .NET framework. I'm not an expert in the differences, just another coder, but there's been a lot of enhancements to C# .NET in the pa

Don't discount C# and the .NET framework. I'm not an expert in the differences, just another coder, but there's been a lot of enhancements to C# .NET in the past couple of years.

foepys 9y ago
Does .NET on Linux really work as well as Python, Ruby, Java, etc. do? Windows isn't cheap and Microservice-friendly.
- davewasthere 9y ago
  Using Docker containers it does.. And .Net Core, even more so... Can completely run on Linux and Kestrel (behind NGINX) is a very fast webserver. https://docs.microsoft.com/en-us/aspnet/core/publishing/linuxproduction?tabs=aspnetcore2x https://docs.microsoft.com/en-us/aspnet/core/publishing/linu...
- quickthrower2 9y ago
  .NET is excellent in my opinion. You have C# striking a great balance between features, performance, type safety and flexibility. Definitely microservice friendly. Azure is reasonably priced with various serverless offerings. And you can just run .NET Core if you want to target Linux and pick a dirt cheap host.
hvidgaard 9y ago
And you can self serve from Linux if that is what you're into.
positivecomment 9y ago
I made a prototype using .NET Core MVC + Entity Framework + Npgsql + Autofac (Probably better IoC containers available out there but I'm used to Autofac open to suggestions btw). It was very easy to develop, test and deploy. Npgsql has support for most of the postgres features (except complex types but that's planned). I deployed everything on Ubuntu servers and runs like a champ. (I'm saying prototype and it is indeed, but it has 100-something users across the globe testing their workflows continuously and it has a lot of CPU-intensive stuff which is child's play with .NET to manage asynchronously. A production app would have two orders of magnitude more users but I think I'll be able to get away with a single server if it comes to that).
- styfle 9y ago
  What was your experience upgrading a dotnet-core app? We had a couple experiments at my company but going from 1.0 to 1.1 had breaking changes so we couldn’t upgrade easily.
  - positivecomment 9y ago
    I think everything was beta-quality until 2.0 - so yeah it wasn't easy. Nowadays it's smooth sailing.

Don't discount C# and the .NET framework. I'm not an expert in the differences, just another coder, but there's been a lot of enhancements to C# .NET in the past couple of years.

foepys 9y ago

Does .NET on Linux really work as well as Python, Ruby, Java, etc. do? Windows isn't cheap and Microservice-friendly.

davewasthere 9y ago
Using Docker containers it does.. And .Net Core, even more so... Can completely run on Linux and Kestrel (behind NGINX) is a very fast webserver. https://docs.microsoft.com/en-us/aspnet/core/publishing/linuxproduction?tabs=aspnetcore2x https://docs.microsoft.com/en-us/aspnet/core/publishing/linu...
quickthrower2 9y ago
.NET is excellent in my opinion. You have C# striking a great balance between features, performance, type safety and flexibility. Definitely microservice friendly. Azure is reasonably priced with various serverless offerings. And you can just run .NET Core if you want to target Linux and pick a dirt cheap host.

hvidgaard 9y ago

And you can self serve from Linux if that is what you're into.

positivecomment 9y ago

I made a prototype using .NET Core MVC + Entity Framework + Npgsql + Autofac (Probably better IoC containers available out there but I'm used to Autofac open to suggestions btw). It was very easy to develop, test and deploy. Npgsql has support for most of the postgres features (except complex types but that's planned). I deployed everything on Ubuntu servers and runs like a champ. (I'm saying prototype and it is indeed, but it has 100-something users across the globe testing their workflows continuously and it has a lot of CPU-intensive stuff which is child's play with .NET to manage asynchronously. A production app would have two orders of magnitude more users but I think I'll be able to get away with a single server if it comes to that).

styfle 9y ago
What was your experience upgrading a dotnet-core app? We had a couple experiments at my company but going from 1.0 to 1.1 had breaking changes so we couldn’t upgrade easily.
- positivecomment 9y ago
  I think everything was beta-quality until 2.0 - so yeah it wasn't easy. Nowadays it's smooth sailing.