The value of a common design language thing really can't be overestimated, I think. I'm working on a new wiki, a new UI for our products, and a new Drupal deplo

The value of a common design language thing really can't be overestimated, I think. I'm working on a new wiki, a new UI for our products, and a new Drupal deployment for our forums/issues/shopping cart. Making all of these look consistent would have been unrealistic on our budget in the past...given that there are now Bootstrap themes for Drupal and MediaWiki (with varying degrees of completeness and quality), it becomes much more reasonable. We may still fail to provide perfect consistency, but it'll be a lot closer than was possible in the past. Also, the "bloat" arguments that I keep seeing are kind of no-op arguments, used against languages, operating systems, applications, etc. when you don't have useful criticisms. "Bloat" means, "it has features I don't use". Which is true of most things that have been in development for a while. It also ignores the ability to roll a custom Bootstrap which is missing the stuff you don't need. Sure there are some inter-dependencies, but nothing too offensive. I like that we now have a higher level abstraction for UI components. I hate it when desktop application designers throw together their own UI components and ignore the OS guidelines and API. That's not to say there isn't room for innovation and novel UI concepts. Just that if you're building a thing with buttons and tables and forms and crap like that, it probably doesn't need to look completely unlike anything else that has ever existed...and it's probably bad design if it does look completely unlike anything else that has ever existed.