4 ms·

I've been trying out tamagui and for what it's worth, it's been a joy. The dev is sometimes a bit slow to respond to some issues, but he's chugging along and do

I've been trying out tamagui and for what it's worth, it's been a joy. The dev is sometimes a bit slow to respond to some issues, but he's chugging along and doing a lot of work for a single person. I really like the theming system and the abstractions, but I hope it gains more traction and more of a team working on it so you can be sure it'll keep being maintained. The starter with nextjs/expo is sooo complicated though. I know it's not tamagui's fault, but the js ecosystem is a terrible mess. Bundlers/monorepo managers/package managers all come together to build a tower so tricky it feels like it will fall at any moment. And that's coming from someone _relatively_ used to it. It's wild to me that this is the best we can do at the browser, I've come to the conclusion that the ecosystem is not fixable. I hope WebIDL and GC in wasm take off and give us more options in the long run.

nwienert 3y ago
I agree it’s way too complex, it’s a problem I’m working on actively. I’d like to first help https://vxrn.dev https://vxrn.dev find some consistent contributors and get it stable. And then I ported Expo Router to work with it, so shared single file system routes and no more need for a monorepo. So now you’ve simplified from two bundlers, two stacks, four folders down to one stack, one bundler, and one folder. And then I have some interesting ideas to make data a lot simpler which I’d like to try on top. All together no reason we can’t make a modern Rails like experience work, but it is crazy how much work it is with all the modern stuff, but imo will pay off with something actually great for universal apps.
- leononame 3y ago
  Thanks Nate for your hard work. I think you're on a great path with tamagui and vxrn sounds great too if it can hold up what you promise. The different bundlers and routers, plus having the workspaces, turbo and things like keeping deps in sync are really a major pain. I understand the need for it, but if you manage to solve this issue as well: kudos. I wish you and your projects a lot of success and I'm looking forward to everything that's coming.

nwienert 3y ago

I agree it’s way too complex, it’s a problem I’m working on actively. I’d like to first help https://vxrn.dev https://vxrn.dev find some consistent contributors and get it stable. And then I ported Expo Router to work with it, so shared single file system routes and no more need for a monorepo. So now you’ve simplified from two bundlers, two stacks, four folders down to one stack, one bundler, and one folder. And then I have some interesting ideas to make data a lot simpler which I’d like to try on top. All together no reason we can’t make a modern Rails like experience work, but it is crazy how much work it is with all the modern stuff, but imo will pay off with something actually great for universal apps.

leononame 3y ago
Thanks Nate for your hard work. I think you're on a great path with tamagui and vxrn sounds great too if it can hold up what you promise. The different bundlers and routers, plus having the workspaces, turbo and things like keeping deps in sync are really a major pain. I understand the need for it, but if you manage to solve this issue as well: kudos. I wish you and your projects a lot of success and I'm looking forward to everything that's coming.