.NET Core vs Mono

Overview

Mono

Stacks94

Followers59

Votes1

GitHub Stars11.4K

Forks3.8K

.NET Core

Stacks7.0K

Followers2.6K

Votes155

GitHub Stars21.7K

Forks4.9K

.NET Core vs Mono: What are the differences?

Introduction

In this Markdown code snippet, we will provide the key differences between .NET Core and Mono. This information can be used to understand the distinctions between these two frameworks and make informed decisions when choosing which one to use for a website.

1. Execution Environment: .NET Core uses the .NET Core Runtime, while Mono uses the Mono Runtime for executing applications. The .NET Core Runtime is designed to be cross-platform and supports Windows, Linux, and macOS, whereas the Mono Runtime is primarily used for non-Windows platforms.
2. Supported Platforms: .NET Core supports a larger number of platforms compared to Mono. It can run on Windows, Linux, macOS, and also on a wide range of mobile (Android, iOS) and cloud platforms. On the other hand, Mono primarily focuses on providing cross-platform support for Linux and macOS.
3. Development Community: .NET Core has a larger and more active development community compared to Mono. This means that there are more resources, libraries, and community support available for .NET Core developers. Additionally, Microsoft actively contributes to the development of .NET Core, ensuring regular updates and improvements.
4. Ownership and Support: .NET Core is developed and supported by Microsoft, making it a more reliable and well-maintained framework. On the other hand, Mono is an open-source project led by the Mono community with support from companies like Xamarin and Microsoft. While both frameworks have strong support, .NET Core benefits from Microsoft's resources and expertise.
5. Performance: .NET Core generally offers better performance compared to Mono. This is because .NET Core is optimized for modern hardware and utilizes Just-In-Time (JIT) compilation, which can provide faster execution speeds. Mono, although performant, may not be as fast as .NET Core in certain scenarios.
6. Compatibility: .NET Core is not fully compatible with the full .NET Framework, which means that some features and libraries may not work out-of-the-box. On the other hand, Mono aims to provide compatibility with the full .NET Framework, allowing developers to run existing .NET applications seamlessly.

In summary, .NET Core and Mono differ in their execution environment, supported platforms, development community, ownership and support, performance, and compatibility. While .NET Core provides a more diverse and well-maintained ecosystem with broader platform support, Mono focuses on Linux and macOS platforms and offers compatibility with the full .NET Framework.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Mono, .NET Core

Anonymous

Dec 16, 2019

Review

There has been a lot of buzz around having PostgreSQL for ASP.NET Core 3.1 web apps. But Configuring Identity Server 4 with PostgreSQL is a real challenge. I've made a simple video to configure the ASP.NET Core 3.1 based Web application that uses AngualrJS as front end with Single Page App capabilities with Identity Server 4 talking to the PostgreSQL database. Check out this Video tutorial on how to do that in detail http://bit.ly/2EkotL5 You can access the entire code here on github http://bit.ly/35okpFj

210k views210k

Comments

Jakub

Jan 2, 2020

Decided

I was researching multiple high performance, concurent//parallel languages for the needs of authentication and authorization server, to be built on microservice architecture and Linux OS. Node.js with its asynchronous behavior and event loop suits the case best. Python Django & Flash turns to be slower and .NET Core & Framework wasn't the best choice for the Linux environment at the time (summer 2018).

I also tested Go lang and Rust, although they didn't meet the quick prototyping criteria as both languages are young and lacking libraries or battle-tested ORM.

377k views377k

Comments

Detailed Comparison

Mono	.NET Core
It is a software platform designed to allow developers to easily create cross platform applications part of the .NET Foundation. It is an open source implementation of Microsoft's .NET Framework based on the ECMA standards for C# and the Common Language Runtime.	Cross-platform (supporting Windows, macOS, and Linux) and can be used to build device, cloud, and IoT applications.
Cross platform ;Open source; Implementation of Microsoft's .NET Framework	Cross-platform; Consistent across architectures; Command-line tools; Flexible deployment; Compatible with .NET Framework, Xamarin and Mono, via .NET Standard; Open source; Supported by Microsoft
Statistics
GitHub Stars 11.4K	GitHub Stars 21.7K
GitHub Forks 3.8K	GitHub Forks 4.9K
Stacks 94	Stacks 7.0K
Followers 59	Followers 2.6K
Votes 1	Votes 155
Pros & Cons
Pros 1 It was great, pre-dotnetcore	Pros 30 Perfect to do any backend ( and a fast frontend) stuff 27 Fast 26 Cross-platform 25 Great performance 18 It promotes better codebase architectures and organizat
Integrations
Entity Framework Mac OS X C# Windows Debian	Linux C# Visual Studio Code Sublime Text .NET Visual Studio ASP.NET Vim Visual Basic F#

What are some alternatives to Mono, .NET Core?

Node.js

Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Rails

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

Django

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Laravel

It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.

.NET

.NET is a general purpose development platform. With .NET, you can use multiple languages, editors, and libraries to build native applications for web, mobile, desktop, gaming, and IoT for Windows, macOS, Linux, Android, and more.

ASP.NET Core

A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core.

Symfony

It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..

Spring

A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.

Spring Boot

Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration.

Android SDK

Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment.

Related Comparisons

.NET Core vs Mono: What are the differences?

Introduction

1. Execution Environment: .NET Core uses the .NET Core Runtime, while Mono uses the Mono Runtime for executing applications. The .NET Core Runtime is designed to be cross-platform and supports Windows, Linux, and macOS, whereas the Mono Runtime is primarily used for non-Windows platforms.
2. Supported Platforms: .NET Core supports a larger number of platforms compared to Mono. It can run on Windows, Linux, macOS, and also on a wide range of mobile (Android, iOS) and cloud platforms. On the other hand, Mono primarily focuses on providing cross-platform support for Linux and macOS.
3. Development Community: .NET Core has a larger and more active development community compared to Mono. This means that there are more resources, libraries, and community support available for .NET Core developers. Additionally, Microsoft actively contributes to the development of .NET Core, ensuring regular updates and improvements.
4. Ownership and Support: .NET Core is developed and supported by Microsoft, making it a more reliable and well-maintained framework. On the other hand, Mono is an open-source project led by the Mono community with support from companies like Xamarin and Microsoft. While both frameworks have strong support, .NET Core benefits from Microsoft's resources and expertise.
5. Performance: .NET Core generally offers better performance compared to Mono. This is because .NET Core is optimized for modern hardware and utilizes Just-In-Time (JIT) compilation, which can provide faster execution speeds. Mono, although performant, may not be as fast as .NET Core in certain scenarios.
6. Compatibility: .NET Core is not fully compatible with the full .NET Framework, which means that some features and libraries may not work out-of-the-box. On the other hand, Mono aims to provide compatibility with the full .NET Framework, allowing developers to run existing .NET applications seamlessly.

.NET Core vs Mono

Overview

.NET Core vs Mono: What are the differences?