Hello Stan,
Thanks for your input on this. We have actually removed a whole load of bloatness in EasyBlog 5.1. Moving forward, we are going to be using our own css framework rather than relying on Twitter Bootstrap.
The idea behind Twitter Bootstrap is perfectly awesome because Joomla uses it as standard but there are different templates by different Joomla template companies rendering different bootstrap versions and different bootstrap styles.
In order for our extension to work fine out of the box with all template clubs, we had to render our own bootstrap library and this is where it all gets really messy.
1. Joomla renders it's own jquery + bootstrap (or mootools)
2. Template company renders it's own jquery + bootstrap (bootstrap 3 or bootstrap 2 or modified bootstrap 3 or modified bootstrap 2)
3. Then, when some template club starts to change the behavior of Twitter bootstrap, is where things turns into a nightmare.
As an extension company, our goal is to ensure that the extension works out of the box without any conflicts. The only way to solve problem #1 and #2, is to render our own bootstrap library.