For those considering switching from Bootstrap to Material or Tailwind or whatever, fwiw PurgeCSS does a really good job slimming down the bootstrap CSS. That, combined with the fact that Angular with standalone components now properly tree shakes the javascript, means that Bootstrap is likely back to being the most performant CSS framework.
I was shocked by how buggy Angular Material is. Some of the CDK stuff is nice but Angular Material, until very recently, deviated from all versions of the Material spec and was just full of issues. I'm looking at you popover.
I'm using Bootstrap 5.x with a Material 3-ish component styles for my current project.
Some common Angular Material gotchas may include...
- Checkbox text doesn't wrap
- There isn't a datetime picker (only date)
- Styling library components / child components is a pain in the ass. Their escape hatch for this (ng-deep) has been deprecated for years without a replacement.
I personally love the fact that BS is being developed actively. I invested a lot of time learning all the scss and mixin files intimately and always appreciated how the team structured them such that it strikes the right balance between turn-key vs customization.
And that’s a valid choice if that helps get your app up and running! I think the goal of the parent comment was to establish how making complex technologies simpler helps us deliver more
Is there any similar CSS framework like Bootstrap, but more oriented to corporate/business use, where complicated data tables are bigger requirement than components to build a landing page?
I think I stopped following Bootstrap since they released 4.0.
I have a feeling that they just tinker around the edges while creating breaking changes so that you can't upgrade your project without doing massive amount of work.
That being said I have a couple of projects running on now you could say ancient version of Bootstrap and they are doing fine.
Maybe they could get my interest if they could explain in simple terms why are they doing all those changes? Otherwise it does not make sense.
How 5.3.0 is better than 3.0? What does it solve in a better way?
I opened some help pages and it seems like an overcomplicated mess. Almost like studying for PhD to create a basic page. Why?
Totally! First, they took the easy way out with a complete rewrite for Bootstrap 4.
"With Bootstrap 4, we once again rewrote the project to account for two key architectural changes: a migration to Sass and the move to CSS’s flexbox. Our intention is to help in a small way to move the web development community forward by pushing for newer CSS properties, fewer dependencies, and new technologies across more modern browsers."
For Bootstrap 5, they didn't even do that much — just new and updated components (including checks and radios), new and updated utilities, significantly-enhanced forms support, RTL support, improvements to the grid system, and more.
I still remember the historical hoopla on major versions. The choice quote below was on their page when the team announced that all v3 development was stopping so they could focus on the alpha v4. Relevant Reddit thread[0].
Supporting
When we shipped Bootstrap 3, we immediately discontinued all support for v2.x, causing a lot of pain for all our users out there. That was a mistake we won’t be making again. For the foreseeable future, we’ll be maintaining Bootstrap 3 with critical bug fixes and documentation improvements. v3 docs will also continue to be hosted after v4’s final release.
Once you use bootstrap, tailwind whatever you are locked in an intermediate abstraction that you won't be able to get rid off unless rewrite your style entirely, most likely break/have to update your design along the way. This should be clear from day 1
They don't mean switching from bootstrap to something else. They mean an upgrade, like switching from bootstrap 3.4 to 4.0 shouldn't require rewriting 90% of your frontend html, and yet it does.
Tailwind v2 to v3 has a few breaking changes but it's nothing compared to bootstrap.
Readit News
I'm using Bootstrap 5.x with a Material 3-ish component styles for my current project.
That's why I chose to go with PrimeNG for our project, which has turned out great.
I have a feeling that they just tinker around the edges while creating breaking changes so that you can't upgrade your project without doing massive amount of work.
That being said I have a couple of projects running on now you could say ancient version of Bootstrap and they are doing fine.
Maybe they could get my interest if they could explain in simple terms why are they doing all those changes? Otherwise it does not make sense.
How 5.3.0 is better than 3.0? What does it solve in a better way?
I opened some help pages and it seems like an overcomplicated mess. Almost like studying for PhD to create a basic page. Why?
Totally! First, they took the easy way out with a complete rewrite for Bootstrap 4.
"With Bootstrap 4, we once again rewrote the project to account for two key architectural changes: a migration to Sass and the move to CSS’s flexbox. Our intention is to help in a small way to move the web development community forward by pushing for newer CSS properties, fewer dependencies, and new technologies across more modern browsers."
For Bootstrap 5, they didn't even do that much — just new and updated components (including checks and radios), new and updated utilities, significantly-enhanced forms support, RTL support, improvements to the grid system, and more.
https://blog.getbootstrap.com/2021/05/05/bootstrap-5/
Once you use bootstrap, tailwind whatever you are locked in an intermediate abstraction that you won't be able to get rid off unless rewrite your style entirely, most likely break/have to update your design along the way. This should be clear from day 1
Tailwind v2 to v3 has a few breaking changes but it's nothing compared to bootstrap.