Difference between Entity Framework and nhib.pdf

Today, I saw a wonderful article on the boy's blog.ArticleAstoria to SQLite to Entity Framework to build your ORM concept. the article tells a lot of wonderful content, from SQLite for ADO. NET 2.0 data provider to the Entity Framework EF, as well as the concept of ORM, lists the complete views of ORM:

This article introduces four aspects of ORM, namely top-down (top-down), bottom-up (bottom-up), and inside-out (inside-out ), outside-in ).

From the perspective of personal experience, nhibco is obviously a top-down approach, and the natural poco support is the best evidence. However, the current V1 version of ADO. NET Entity Framework should be bottom-up in the bottom-up mode. Ado. NET Entity Data Model Wizard is the best evidence. If Entity Framework V2 supports poco, the vertical dual-direction support can be achieved, but this is not enough, as I will describe later.
As for inside-out, outside-in is a place that truly shows the power of An ORM tool or an E/R Model programming model, because 99% of the real world and databases are neither synchronized nor synchronized, it is very important to provide support from the inside out and from the outside. In fact, the existence of ORM and DP is to implement the capabilities and support in both directions, otherwise there is no need to exist, because top-down and bottom-up) the two methods have been around for a long time. To solve these two problems, Orm tools or E/R Model programming may not be the best method, because these two directions and thinking are not objective, it is assumed that the real world and data are the same, or we can control it on our own. In fact, this idea is unrealistic.

Similarly, think carefully about the support provided by Entity Framework (maybe as well as nhibframework) in the outside-in direction, which is often said by EF daxie, represented by dsimmons, entity Framework is not a simple ORM tool. It mainly provides an E/R model that is completely close to reality. This model can be used for data programming (DP) or modeling and data presentation, the most important thing is that this model can be shared and reused (a successful case is that it can be used by ADO.. NET data service sharing and reuse). In addition, the functions of SQL Server are gradually enhanced, and the functions of database + dp, such as LINQ, are mixed and explosive, in other ways, mapping can be limited to some functions and scenarios. In this case, Entity Framework seems to be moving in this direction. In fact, this is also a more likely and effective development philosophy-from this perspective, EF's current ORM/mapping problems are also It is easy to understand.
On the contrary, the internal-out (inside-out) method is difficult for me. Let's assume that we have a omnipotent mapping/ORM technology or tool first, then we will use it to connect the changes and gaps between the real world/OPP and data storage/database. This ..... I may have misunderstood it.

From the above description, we can clearly see the differences between Entity Framework and nhib.pdf. Although they are all ORM tools, they have different focuses in different aspects of ORM.