orats VS Hobo

I used to maintain https://github.com/nickjj/orats since 2014 but I consider the above repo a successor to that. It's not easy to end up with a production ready solution when you try to cobble together a bunch of independent little templates but it is possible when you have a single baseline app which you could then add your opinionated gems to afterwards.

I'm not looking for the overthrow of CRUD-through-MVC. Rather, Hobo and Hoodie seemed like advances---Hobo was sort of Rails for Rails, and Hoodie was an offline-first framework for something like what we now call Progressive Web Apps---when I tried them early in their life-cycle, but both seem to have withered away. And nobody else (that I can find) seems interested in improving graphical design (as in, "just use Material Design, or Carbon, or whatever"), cleaner parent/child relationships, automatically updating views and controllers to match changes to the models, and probably features that I don't know that I need.