Thanks for the feedback!
453 karma · joined December 28, 2016
Check out my work: https://avo.cool - Admin panel framework for Ruby on Rails that saves your time. Move 10x faster without writing boilerplate code https://basetool.io - View and manage all your data in one place like a pro
Thanks for the feedback!
Thanks for the feedback!
To answer your question, basetool is only a proxy between the browser and your data source when it comes to your data. We don't store any of your data at any point in time. We also purposefully haven't created any tooling that impersonate users accounts while an admin. Those are not our intentions.
Regarding meta-data, we are storing the table names and column names when a user creates a setting on them, but that's about it. We're not storing any or the queries made queries either.
Regarding telemetry, we don't collect any for the self-hosted version. We should probably add some, with opt-out of course option and anonymized too.
Yeah, I agree. That's not the way to go. Components is the way to go.
Regarding using tailwind in general, I had a few issues in the beginning, too, until I figured out how it's supposed to be used.
It is a bit tough to use it with frameworks that don't allow you to create components in a more modular way. But if you get to create these components, it's really a joy. It reminds me a bit of the BEM methodology (just a bit).
Again... it's also a matter of what each person is vibing with.
I'm not the one to say if what we choose will last in the future, but we really are not afraid that they will be gone in the near future. The technologies we picked are not the "hot new thing", and we just picked them up.
If I can use your metaphor, I'm not sure we could have built this in COBOL. We chose the tools that we thought were best at this moment in time.
Thank you!
Avo was first a Rails-backed SPA (Rails server and Vue front-end), and it didn't work out that well. Unfortunately, the Rails community didn't take that lightly, and for a good reason. I won't go into too much bike-shedding here, but the most important reason is that you have to maintain two codebases (ruby & JS).
In January, we re-wrote Avo with Hotwire (the JS front-end suite created for Rails), and it went very well. It's a joy to write apps using Rails and Hotwire.
But the fact of the matter is that we need an app that's a bit more dynamic on the front-end than Hotwire can deliver. I mean, yes, we could weave together Hotwire and a few other JS libraries to get what we need, but we'd get the same two codebases and the same two sets of skills you need to run your app.
The reason we chose to go with React is the ecosystem, mostly (*fun fact; I'm sitting here writing this wearing a VueJS hoodie). We're running Next.JS because, honestly, it's a beast when you're talking about React apps. TailwindCSS because of its popularity, and it vibes with us, and we move fast using it. Prisma because it really is a breath of fresh air when you consider the alternatives in the JS world.
I left TS at the end because it's the most "well-known development secret" out there. It keeps your codebase in check and your team on the same page.
Thanks!
PS: What are your impressions about basetool?
Now in open beta.