the visual builder still relies on knowing fundamentally what a db is, what a join is. like mega obvious stuff that actually isn't obvious to non technical people.
we area also multi tenent and it's not the best for that. like the default permissions when you add a db are broad, the organization of dashboards, questions, etc is not great. through different versions they have re organized and stuffed things oddly.
i've also messed up the elastic beanstalk a few times. i am not even close to an expert on aws so might just be me being stupid.
probably worth just paying for their service in the end..
There are maybe 1/10-1/5 or maybe more who will be enabled by them on a technical level. The same kind of people who will build a site out of WP themes and plugins or build quite involved spreadsheets and so on.
I think it’s generally important and useful to enable and respect power users like that. They occupy a unique niche.
Also, "everyone nervous" is an interesting choice of words - I'm pretty sure most people wouldn't really care one way or the other. What is it about AGPL that causes stress among the masses?
Things like Google's AGPL internal policy[1] existing as a public piece of corporate-friendly IP propaganda have snowballed into a lot of FUD about the license.
People like to parrot perceived and secondhand opinions about the AGPL, and "some companies don't like the AGPL" transformed into "the AGPL makes everyone nervous."
[1] https://opensource.google/documentation/reference/using/agpl...
Clarifications: no, using the tool directly is not a problem for us.
"Everyone" - appreciate your question and not guessing :-) I meant everyone at my company. That phrasing maybe speaks to my mindset :-D Basically I really mean legal and those in charge who might listen to legal over tech.