Playing devils advocate on this one. This addresses using bootstrap with className prop, not the react-bootstrap which is a wrapper for react. Bootstrap can be for intranet style applications where design does not really matter. Furthermore, it can be enhanced by simply adding more styles to the style prop without having to to dive into the flexbox. Going on further, Next.JS is disgusting and a step backwards in my opinion. React sole purpose was for SPA and Next.JS attempts to break that. Frontend should solely be frontend, and backend should be backend. I started programming with PHP where frontend and backend was one in the same. Working with this in the professional field is such a headache. Digging through tons of UI code to fix some backend code. Modern browsers are more than capable of rendering components, so rendering it with your server is just a waste of resources .
keep calm ... but tailwind is not usable in every project, and with practice (and nodesass) bootstrap make job as good as tailwind on every point. I use both personally, and i think the word "Learning" on a css framework is overkill Yes if I have to dev a react/next project, I will switch on tailwind but its not automatic
Because it makes developing a WebApps much more faster
My favorite part is when u went to shadcn... lol😅😂😆
❤❤
Playing devils advocate on this one.
This addresses using bootstrap with className prop, not the react-bootstrap which is a wrapper for react.
Bootstrap can be for intranet style applications where design does not really matter. Furthermore, it can be enhanced by simply adding more styles to the style prop without having to to dive into the flexbox.
Going on further, Next.JS is disgusting and a step backwards in my opinion. React sole purpose was for SPA and Next.JS attempts to break that.
Frontend should solely be frontend, and backend should be backend. I started programming with PHP where frontend and backend was one in the same. Working with this in the professional field is such a headache. Digging through tons of UI code to fix some backend code. Modern browsers are more than capable of rendering components, so rendering it with your server is just a waste of resources .
because of university syllabus
sed life
keep calm ... but tailwind is not usable in every project, and with practice (and nodesass) bootstrap make job as good as tailwind on every point.
I use both personally, and i think the word "Learning" on a css framework is overkill
Yes if I have to dev a react/next project, I will switch on tailwind but its not automatic