HMVC the right way ?!

I disagree ... Libraries are supposed to be portable, not dependable on the application that uses them and you don't get that when a library uses a model.

You should be able to take a library, drop it in another application and work with it with no changes necessary. A model on the other hand is designed for a specific application. That's the only difference between the two.

Agreed on both these counts.

My 2c, HMVC is not the right way to code. Just look at all the trouble you guys are having just trying to make it work. Not only that, what about when you develop something and some noob jr dev comes along and tries to maintain it. Or how about the original dev leaves the company and someone like me has to support it.

I have my own code in Codeigniter that I can take from 1 project and plant into another. It's called libraries. Things like auth, scrapers, cron, payment gateways. you name it, i have it and within minutes, I have something dropped in.