+1 @DMehaffy
We define ourselves as a CMS because we are one, but also to not disappoint the current and future users. The product is going into a direction to become an, even more, better CMS, not backend framework. Our roadmap includes Reviews & Publication workflows, Content History, Audit Logs, Notification Center, a better Draft & Publish system, managing content per communication channels/devices, etc. We want to help you to write better, faster & stronger content.
Technically, you can remove the administration panel, and do everything by code; we will always try to make things optionable for everyone, but we might have to make choices that would benefit most the CMS users than the backend users.