Hey! Thanks for reading. 🚀

I might have overlooked it but the reason I say it is more organized and easier to maintain is because when you create a class rather than a plain object (POJO), it "easily" gives you the idea on what is it all about, hence the blueprint. I think in a plain object, it doesn't give you that idea like "grouping" thing. Or maybe it is a psychological thing? Like I feel I am more organized in classes due to the spaces in between, the declaration or grouping of methods (not having to inline), having a "structured" way to show what it is all about rather than a plain object (POJO) which I think is the alternative of those. Although I think you can still make it "clean" and apply those type of code style & cleanups.

In regards to the BASE_URL that you mentioned. I think it is a constraint that is good to have. It is intended that no other class or subclass need to have access to it. I think to avoid the issue with the usual inheritance is to limit it and design your classes in a way it strike the balance between being classy and not.

Appreciate your feedback. After all, everything is subjective. Not everything is "easy" or "clean" to others. I think it's good we share different points of view as it gets me the chance to learn more from your perspective. Thank you! 😊