Is it just me, or does this seem like a solution looking for a problem? Especially the verbose way the ORM works... just seems overly complex without actually solving any real problem I had with ActiveRecord.
separation of the entities and repositories is useful in many ways.
For example, you can stub the repository and avoid persisting objects in tests, and only test persistence in the appropriate ones.
Or, you always know that operations you call on an entity won't touch the database, so you avoid a whole class of problems (think: accidental N+1 queries in a loop).
Or, by making the query interface private to the repository, you avoid accidental leakage of storage details (think: `default_scope` impacting associations)
It's not just you, as I was scrolling the article I was looking for "what's the improvement over other frameworks like ActiveRecord or Sequel?"... I didn't see anything.
Anyone have commentary on why one would use this over another more mature framework?
The ORM isn't he selling point of Hanami. This is just an announcement for an ORM.
IMHO, if popularity was a concern, Luca should have opted for a batteries included nosql ORM/DB with seemless integration. Couchdb and MongoDB would have made excellent candidates.
