They've gone full circle: this is bootstrap implemented in tailwind. How funny.
EDIT: It is funny because I've been looking for something opinionated like Bootstrap, but that can be tree-shaken to a smaller package, like Tailwind, but I don't want have to redesign every dang component.
Thanks! I went to shuffle.dev and saw "Start a new project with one million layouts!" That's a big number, but hoo boy, I gotta search through all these? Well, I've got a project for lunch it seems!
Similar for me, Next.js / Daisy + Tailwind / Firebase means I can whip out a MVP or prototype in weeks instead of months. Love the increase in productivity first tooling in web development ecosystem.
interesting...in what ways do each of those boost your productivity? And what is the amount of effort to take that MVP to a production state?
I guess the only missing piece there is a backend API.
I bought Chakra and now kind of regretting, seeing all the free stuff, Daisy for instance is something that I never heard of until I saw the comments here.
Next.js creates a good setup to create a React frontend application with server side rendering support out of the box. Pair that with Vercel and you get an amazing deployment environment with CDN, cloud functions, edge functions (middleware) server side rendering and more without much hassle.
Tailwind let me quickly create any UI I want, and Daisy helps me reduce the amount of time needed to style basic elements like inputs and all.
Firebase lets me get a low latency real time data source for my application, that can scale infinitely. It also handles some other parts of building an application that normally take a lot of time: authentication, storage management etc. And the pricing is really really cheap once you consider how much it costs to create an infrastructure that scales as well as firebase does, unless you model your data wrong and end up using a lot of db read/write cycles unnecessarily.
The backend API piece is not missing, you can use either Next.js API or firebase functions for backend piece, I use those for things like stripe billing backend etc.
This stack is enough for most projects out there, and when its not enough its flexible enough that you can integrate it with other things. And that timeline I mentioned was for a production ready MVP.
I see it's great for building an MVP but may not be a good fit outside of startups. Nevertheless, its the front-end and server side rendering is quite interesting to me.
What are some problems with this setup? Might have a go just for the frontend portion but seems to good to be true in some aspects.
Hah, I'm a bad person to ask because I'm managing now. I've used much more React professionally, but I still find myself much more productive in the Vue ecosystem.
I don't often collide with company cultures that require specific language/tool experience in my network these days, though I realize they exist out there. I haven't ever hit an issue launching into a job in unfamiliar languages, and I've made that leap with all of Ruby/Java/Golang/PHP/Python – minimal pre-exposure in every case (school was C++).
Right, yeah a new programming language is like driving a new car, you check for how it does all the primary concepts and learn about the one or two new concepts
Lots of recruiters and hiring managers dont see it that way
EDIT: It is funny because I've been looking for something opinionated like Bootstrap, but that can be tree-shaken to a smaller package, like Tailwind, but I don't want have to redesign every dang component.