Hello everyone,
The high-quality documentation for my ORM framework is now complete: Jimmer, revolutionary ORM for java & kotlin
Based on suggestions from a group of Jimmer users, I spent a full four months writing this high-quality documentation.
In the past, I’ve introduced this ORM framework before, but for over a year prior, I invested 100% of my energy into continuously implementing planned features, with no time to write quality docs to tell more users what Jimmer actually is.
Now, the high-quality documentation is finally complete. It not only clearly shows what the current 0.8.23 version of Jimmer has accomplished, but also tells users what features it will add in the future.
JVM ecosystem has never lacked ORMs, people even think the competition for ORMs is over. But why am I still creating a new ORM?
-
Traditional ORMs provide an OOP programming model, which is very convenient, but lacks flexibility.
-
Non-ORM lightweight SQL template solutions have fine-grained control over SQL, which is very flexible, but requires huge amounts of work.
A good solution must achieve the best of both worlds, this is the first reason.
The second reason, in fact, completing CRUD database access is only the most basic and simple part of actual projects. There are other pain points that have always plagued developers.
Simple problems keep getting repeatedly solved, while truly complex problems are constantly ignored. I really hope to solve these truly complex problems. Therefore, I have contemplated these problems for over a decade, eventually summarizing a methodology, and providing abstraction and implementation.
Jimmer will bring tremendous value. If it obviously makes developing projects much easier for everyone, that will be the greatest reward for my persistent efforts thus far.
- maybe try to author a “summarizing” article, and multiple parts about the various features for the more curious ones 