Why I Replaced ActiveJDBC With My Own ORM
java
dev.to
Why I Replaced ActiveJDBC With My Own ORM I'm building Obsidian, a Java web framework. The database layer used to run on ActiveJDBC. Then I ripped it out and wrote my own. Not because ActiveJDBC is bad. But because a framework that depends on another framework isn't really in control of itself. The Problem With ActiveJDBC ActiveJDBC lets you write User.where("active = ?", 1) — but Java has a fundamental issue: an inherited static method doesn't know which subclass it's