What are the reasons not to use bootstrap?

Reasons for not using bootstrap: 1. Bootstrap does not perform well in terms of scalability, reusability and maintainability, which greatly increases the workload and difficulty of website developers; 2. It is not easy to integrate and use. It is easy to conflict with existing settings; 3. The file is too large and has too much useless content, which can easily cause the website to load slowly.

The operating environment of this tutorial: windows7 system, bootstrap3 version, Dell G3 computer.

Reason for not using bootstrap:

1. Bootstrap is not the optimal design and does not follow best practices

Usually, the simpler the front-end code of a web page, the better the loading speed and search engine friendliness of the website will be. But when we use Bootstrap to build front-end code, we must use the DOM elements defined by Bootstrap, which is fatal for concisenessists, and Bootstrap does not perform well in terms of scalability, reusability and maintainability, which greatly increases the The workload and difficulty of a website developer's work.

One of my main problems with Twitter Bootstrap is that I end up with a bunch of DOM elements filled with classes. This breaks one of the basic rules of good web design, HTML is no longer separate from semantics and presentation from content. People with front-end mysophobia will find it quite irritating, because it is a challenge to scalability, reusability and maintenance. Twitter Bootstrap also exacerbates the problem of progressive enhancement where presentation and interaction are no longer independent of content.

Uh...there are so many unnecessary classes!

2. Bootstrap is not easy to integrate and use, and it will conflict with my existing settings

If you are airdropped into a large project that is half done, want to What about using Twitter Bootstrappy to enjoy all its benefits? Worse, you'll run into a host of problems, starting with generating HTML, CSS, and JavaScript. Then there are their resources, and you have to dig into those dark corners of the project and figure out which scripts and styles need to be removed or replaced. Twitter Bootstrap will potentially create extra work, and as you get deeper into the project you will inevitably find and fix the odd bug, and the reasons you justify yourself will defeat the purpose of using it in the first place.

3. Bootstrap is too big and has too much useless content

Frankly speaking, Twitter Bootstrap includes 126kb of CSS and 29kb of JavaScript. If you want to use all the features of Twitter Bootstap, you should carefully consider the load time of resources. Of course, for some places this might not be a problem, but in New Zealand the internet has to go across the Pacific and the data will be slow to get there. So consider your target market. Twitter Bootstrap will help you build an attractive, responsive website, but some mobile users will be turned off by slow loading times and battery-hogging scripts.

4. "Halo! My new website looks just like everyone else's!" - Bootstrap is too popular

Twitter Bootstrap is super popular, so almost every Every developer will use it. While it's certainly possible to customize your app or website design later, you may find that time constraints force you to stick with a lot of vanilla Bootstrap style. This can lead to unintentionally creating a lot of similar, generic and memorable websites. Because it’s so quick and easy to use Twitter Bootstrap out-of-the-box, innovation is often discarded as a result. When you have tight time constraints, distinctive and innovative designs are difficult to achieve in the structured environment of Bootstrap.

Related recommendations: "bootstrap tutorial"

The above is the detailed content of What are the reasons not to use bootstrap?. For more information, please follow other related articles on the PHP Chinese website!