What kind of framework is friendly to developers?

1. How far is cloud native from .NET development?

The concept of cloud native has a long history. The story begins with "going to the cloud", with the launch of doker, k8s and other technologies, as well as CNCF and major cloudsWith the joint blessing of manufacturers, cloud native is gradually known to everyone.Cloud native does not depend on a specific cloud, whether public or private.The birth time of .NET6 is very consistent with container technology. .NET6 now fully supports CGroups v2, which is better than Java's support for containers.Next, the introduction of new features such as Native AOT in the .NET 7 version shows that .NET has been making great strides toward cloud-native improvement, and .NET is now ahead of other development platforms in the cloud-native field.

2..NET is suitable for what kind of scenarios?

When we talk about cloud native and microservices, we often mention concepts such as DevOps, CI/CD, etc. For .NET, it is nowVery well supported..NET can also do machine learning, we have tensorflow.net.In terms of cross-platform, there is now an excellent project such as MAUI for everyone to use.There are also a lot of solutions in the IoT industry. NET..NET can do large-scale projects, and it is also very suitable for small and medium-sized projects.Now. NET is open source, and everyone can contribute their own strength. For example, MASA Framework, which is open sourced by the MASA technical team, is a very good case in China.

3. What kind of framework is friendly to developers?

A good frame has three characteristics:

1) Painless Getting Started

A good framework should allow developers to get started quickly with low cost, rather than setting a high threshold.For example, when developing regular projects, you can get started quickly (for example, in a few hours).When you need to go deep, you can go in very smoothly. For example, Spring Boot is a good framework. After .NET Core comes out, .NET Core is even better.

2) Fool-proof design

When developers encounter problems, a good framework allows developers to solve problems naturally and intuitively, without relying on documentation.When an error is reported, there is sufficient information to inform the developer and give a corresponding solution.The component design of winform and WPF is very in line with the fool-proof design. The same Blazor has many optimizations in this regard compared to the previous js framework.A good framework should keep the "KISS" (keep it simple and stupid) principle, simple and foolish, and have principles, not to spoil developers.Many frameworks are "small and beautiful" at the beginning, but in the later stage, the demand continues to increase, and they become bloated and "different".

3) Can be stepped in depth

After starting, you can go deeper in a step-by-step manner, such as learning one usage in 3 days, and then in-depth another usage in 5 days.It allows developers to quickly and deeply grasp when dealing with advanced scenarios.

4.NET is already a very good framework, why should .NET be packaged twice?

Most of the time, with the development of the project, there will be repetitive and non-functional applications outside the business, and some encapsulation will be carried out more or less.Different scenarios require different frameworks. Now, in addition to MAUI and Uno Platform, .NET cross-platform supports other frameworks, which can supplement the requirements of different scenarios. For example, Uno can replace MAUI to support Win7/Win8.The output of .NET is a tool class library. The framework of secondary encapsulation of .NET cannot be just a collection of functions. It must have its own best practices and concepts, but it does not limit developers.

MASA Framework hopes to export our best practices to .NET developers to help you open up a new modern application development experience!