I believe that no tool is perfect. Not even Rails. We reach for other gems and sometimes do things not "the Rails way" and we get the job done.
And there's a fallacy there. We don't go saying "Rails doesn't do everything I need it to do, so I'd rather spend more time to write my framework from scratch". But we're (and I'm including myself too) very quick to say things like that about certain tools just because "it's never been done before", "Nobody uses an off-the-shelf package to build their app on", "I'll hit a ceiling with it...", and so on.
Yes, Avo isn't perfect, and yes, Avo isn't right for any kind of project. There are some that are more suited and some that aren't. Sometimes you might hit a "ceiling" with Avo, but I baked in a ton of "escape hatches" (add own content on multiple levels, override views, override controllers, multiple ways of interacting with the data, Stimulus JS). Using these "escape hatches" (I gotta stop using that term), will help you get the job done.
This message is not fingepointing towards you or anyone else, and I respect everyone's way of doing things, but we should take some time and reflect on that. We don't go and build linuxes, nginxes, pumas, railses and other pieces of tooling everytime beacause we might get stuck at one point. We make it work. Same should apply with pieces of software like Avo.
And there's a fallacy there. We don't go saying "Rails doesn't do everything I need it to do, so I'd rather spend more time to write my framework from scratch". But we're (and I'm including myself too) very quick to say things like that about certain tools just because "it's never been done before", "Nobody uses an off-the-shelf package to build their app on", "I'll hit a ceiling with it...", and so on.
Yes, Avo isn't perfect, and yes, Avo isn't right for any kind of project. There are some that are more suited and some that aren't. Sometimes you might hit a "ceiling" with Avo, but I baked in a ton of "escape hatches" (add own content on multiple levels, override views, override controllers, multiple ways of interacting with the data, Stimulus JS). Using these "escape hatches" (I gotta stop using that term), will help you get the job done.
This message is not fingepointing towards you or anyone else, and I respect everyone's way of doing things, but we should take some time and reflect on that. We don't go and build linuxes, nginxes, pumas, railses and other pieces of tooling everytime beacause we might get stuck at one point. We make it work. Same should apply with pieces of software like Avo.
Thank you for the message!