3 ms·
I'm currently a .Net programmer (C#/MVC). But we're just developing in-house business systems, on a mostly Windows network which it is well suited for. If you'
by Someone1234 10y ago
I'm currently a .Net programmer (C#/MVC).
But we're just developing in-house business systems, on a mostly Windows network which it is well suited for. If you're actually doing a "large web application" (distributed?) I'd likely still recommend Java on Tomcat.
Why? .Net's biggest strength as a platform is that it hooks into other Microsoft services and technologies (from AD, to Sharepoint, to Office 365, to Azure, and beyond).
.Net's biggest drawback, at the time of writing, is still licensing. .Net runs in IIS on Windows Server. Yes, I know, .Net core is on Linux but that isn't near production ready. So for the next year or two you'll be paying for Windows Server which is pricey (both literally and because the hardware per user is lower).
Java on Tomcat running on Linux is cheap. Very cheap. And it is a tried and tested platform that has been used at almost all scales (from small bespoke business applications up through distributed goliaths).
I actually prefer C# to Java in terms of programming language. I also prefer how the .Net libraries are laid out and how thoughtful even down to method overloads are. But ultimately language and library choice should play second fiddle to platform choice and cost/benefit analysis.
If you're doing bespoke business applications in a business with a Microsoft network, .Net may make the most sense. If you're exposing it to the world as a service, I'd do Java or in some cases look at Ruby on Rails or something else.
- UK-AL 10y agoRunning a huge e-commerce site using .net has been pretty good for us.
- Nelkins 10y agoIt has been good for Jet.com also.
- stan_programmer 10y agoJet.com is all in F# at that...
- WorldMaker 10y ago.NET Core seems production ready enough today. The IDE tooling is still playing catch-up, and so too are NuGet package updates to target .NETStandard still playing catch-up, but in terms of running a finished app things seem solid. Even if you aren't using .NET Core yet, I also think Azure's web hosting is comparable enough in price to other similar offerings that there's isn't as big of a deal about a "windows tax" for website hosting as many think. Even with something like AWS Elastic Compute while there is an extra cost to Windows VMs it is not that much more expensive if you'd prefer to use the .NET stack. (That said, I've wound up using Node a lot more than .NET for websites lately for conveniences having nothing to do with cost such as isomorphic development.)
- garaetjjte 10y agoWhy use .NET Core, while there is Mono?