twitter-bootstrapreact-bootstrap

Advantages of using react-bootstrap over bootstrap


What's the point in using react-bootstrap over plain old Bootstrap?

I was going through https://react-bootstrap.github.io/components.html and I don't see any advantage. I can only see that it can bring unnecessary dependency to the project.

Deducing from reading https://react-bootstrap.github.io/introduction.html the only thing that react-bootstrap gives me the shorthand for class names? Below are the examples of the same page.

In plain Bootstrap I'd do:

var button = React.DOM.button({
  className: "btn btn-lg btn-success",
  children: "Register"
});

React.render(button, mountNode);

And in react-boostrap:

var button = ReactBootstrap.Button({
  bsStyle: "success",
  bsSize: "large",
  children: "Register"
});

React.render(button, mountNode);

All these bsStyle, bsSize, ... from react-boostrap are the things people didn't like in Angular that have to remember all those ng-* tags... I personally don't mind it but if it's the only thing that react-bootstrap gives me I will use Twitter Bootstrap. Or did I miss something?


Solution

  • React-bootstrap creates React components for you.

    The advantage will be obvious if you consider how to do animations with the help of bootstrap in your React project.

    Without react-bootstrap, you need something like CSSTransitionGroup. You cannot take advantage of bootstrap's API because it will manipulate the DOM, which makes the React behavior unpredictable. Also, bootstrap will hide details of their animation API; that is to say,you cannot use it at all.

    With bootstrap components, however, you do not need to worry about how the animation is implemented by bootstrap, you just need to specify properties and hooks in a component and the library will do the trick. More specifically, it can add some wrappers which are not visible to the client.

    enter image description here

    As you can see above, <Fade> and <Transition> component is added by bootstrap.

    In addition, the syntax of virtual DOM may not be compatible with DOM:

    enter image description here

    As shown above, putting <input> inside a <select> is a way of semantic UI, but React will complain. I expect the bootstrap may experience similar issues without a customized library.