That's a great mission statement.
FYI, I think the choice of `tailwind` vs `shadcn` is too hard for JS beginners (like me). I would prefer that you make a choice yourself for the default case and leave the other option to be activated by params in the command line for the folks who know what these two frameworks actually do.
thanks for the great feedback, Vitor!
what I'm trying is to create various templates with different setups.
one with "Tailwind+Shadcn", one with just "Tailwind", one with something else, and that's not just limited to CSS frameworks, Osty should support Svelte, React/Nextjs, Vue/Nuxtjs, Vanilla JS, and yes we need to create templates for all these combinations!
it's just like what Vite does.
one can simply choose their preferred template provided in Osty CLI.
PS: but believe me or not, there is nothing simpler than shadcn right now 😁
I don't know if that is a good idea. It seems like too much. If your goal is to trully have quick and small apps everywhere, then the choice of the framework doesn't matter as much.
right. but I want to provide tools for not only React developers, but also Svelte, and Vue, and other common frameworks as well! this would widen the reach of Nostr I guess.
Yep, but you run the risk of trying to do too much. This is going to be a lot of code to maintain. And since these frameworks change fundamental things quite frequently, it's possible that it gets to be too much to maintain by a single repo.
Years ago, I had an employee that tried to keep a framework with Angular and Ember at the same time (at the time they were the two main frameworks). The project didn't last 6 months before he completely gave up. :(
couldn't agree more! it's a headache! and to be honest it demands a team of 10 😁 I personally will focus on React for now.
My framework of choice. Can recommend.
