When comparing Bootstrap vs mini.css, the Slant community recommends Bootstrap for most people. In the question“What is the best CSS framework?” Bootstrap is ranked 2nd while mini.css is ranked 4th. The most important reason people chose Bootstrap is:
Ranked in these QuestionsQuestion Ranking
Pro Consistency across browsers
Pro Responsive design philosophy
Bootstrap is developed to be instantly compatible with all sizes of screens, so you don't have to worry about which device the user is accessing your site from. Yet if you prefer, you can disable responsiveness of Bootstrap.
Pro Well documented
Documentation is thorough, well organized and full of live examples and templates ready for use. Every component and every part of the framework is explained and covered in depth.
Pro Designed to get a site running quickly
Bootstrap is designed to get a site up and running quickly. Each of it's components is pre-configured to help with getting a site up and running quickly.
Pro Great community
Bootstrap is very popular and has a large community. As a result of this it is much easier to find help with anything you might need. This also gives you a treasure trove of prebuilt components to use and add to your site.
Pro Supports responsive embeds
Allows easily adding responsiveness to
Pro Easily make professional looking websites
Bootstrap makes it easy to learn how to make professional looking websites. It can even make code junkies semi-enjoy design.
Pro Custom builds
Bootstrap can be customized in a variety of ways. Either by overriding the default CSS styles with new CSS styles or by editing the
.scss Bootstrap files.
Pro A wide variety of themes available
To help you avoid the "Bootstrap look", there are many resources that provide a great selection of themes and templates for Bootstrap.
Pro One of the most popular ones
Ranked on GitHub as the most starred CSS repository.
The whole framework is built on flexbox and works really well on most platforms.
Pro Active developer
The developer is actively maintaining the project and responding to any issues and questions.
The framework is really tiny, under 7KB gzipped.
This is what makes mini.css stand out, because it looks like a pretty powerful library and it still is under 10KB.
It works great on all devices, mobile websites are really easy to develop and view.
Few flavours so far, but there is a lot of space for customization.
Pro Great documentation
From basic syntax, templates, examples, customization to-dos and don'ts. The documentation is pretty great.
Pro Supports CSS custom properties (var)
No other framework supports CSS variables right now (as of November 2017). The latest alpha of mini.css supports this feature, making customization even easier.
ARIA rules are a priority and it works very well for all users.
Works really well with screenreaders.
Con Large file size out of the box
Bootstrap has an out-of-the box filesize of ~276K, which is pretty large considering it's just CSS. Most of those styles aren't even used in 90% of web pages built with Bootstrap. By only including the required styles it can be trimmed by 70%-75%.
Con Websites can start to look the same
If the initial Bootstrap colors and styles are not changed or edited, different websites start looking the same even if they have nothing to do with each other and they are made by different developers.
Con Too many classes
Bootstrap's over-reliance on HTML classes for styling can get very messy very quickly. There's also an overabundance of DOM elements which have a lot of classes and are more often than not nested inside DOM elements with even more classes. This gets problematic down the line because the maintainability of the project gets harder when the project starts to get large.
Con Hard to customise
It's quite hard to customise Bootstrap using pre-processors like SASS and LESS, the only real flexibility is with typography and colours.
Con Not widely used
A large community is always an advantage especially for open source projects. It means better documentation, continued development, and lowers the possibility for the project to be abandoned in the future since the probability for someone from the community to keep maintaining it is larger if the community is larger.
Git repo has been archived so it's pretty unlikely to receive bug fixes or new features.
Con Single developer
There is no team developing this framework, except one guy.