Five reasons for not using Twitter Bootstrap, twitterbootstrap

Five reasons for not using Twitter Bootstrap, twitterbootstrap

In our previous blog articles, we discussed the benefits of using Twitter Bootstrap in web design and development projects. Twitter Bootstrap also has many disadvantages. Let's take a look at these main problems:

1. It does not follow best practices

One of the biggest problems we encounter when using Twitter Bootstrap is that your DOM elements are crowded with a large number of classes. This breaks one of the good basic web design rules. HTML does not have semantics, and content and representation are no longer separated. The frontend purist will think this is quite annoying, thinking that it brings scalability, reusability and maintainability to a greater challenge. The representation and interaction are no longer independent of the content which is further enhanced in Twitter Bootstrap.

Oh, so many unnecessary classes!

 

2. It will collide with my existing settings

What if you were dropped to a half-done project and want to use Twitter Bootstrappy to enjoy all of its benefits? Worse, you may encounter a lot of problems. Conflicts first start with generating HTML, CSS, and JavaScript. Then there are their resources. You must go deep into the dark corners of the project and find out which scripts and styles need to be deleted or replaced. Twitter Bootstrap will potentially create additional work. When you go deep into the project, you will inevitably find and fix strange errors, and your reasons for defending yourself will defeat your preferred purpose.

3. Twitter Bootstrap is too heavy

Frankly speaking, Twitter Bootstrap includes kb CSS and 29kb JavaScript. If you want to use all the functions of Twitter Bootstap, you should consider the resource loading time. Of course, this may not be a problem for some places, but the Internet in New Zealand has to span the Pacific Ocean, and it will be very slow to reach the data. Therefore, consider your target market. Twitter Bootstrap will help you build an attractive and responsive website, but some mobile users will not reject it because of slow loading time and power-consuming scripts.

4. SASS is not supported

It may be one of the biggest arguments. BootStrap uses Less construction and native does not support Compass and SASS. Please do not misunderstand what I mean. Less is good. I used it before, and it certainly has its advantages. However, SASS is better, with a framework similar to Compass. Using It seems to require no extra consideration. Some people have built the Bootstrap of Compass gem, but frankly speaking, you will have to use Less. In future articles, I will discuss SASS and Less more. At the same time, Chris Coyier has written an article to compare the two.

5. "Hello! My new website looks like everyone else !"

Twitter Bootstrap is so popular that it is popular that all developers and their dogs use it. You may find that due to time constraints, many native Bootrasp styles are forced to be used to customize your app or website. This will lead to unintentional creation of many similar, general and non-blind websites. While Twitter Bootstrap is fast and easy to implement, creativity is often the result of compromise. In a limited time period, it is difficult to implement innovative designs that break the regular pattern in the Bootstrap structured environment.