I don't disagree with what you are saying either. It can be called a framework, but without context I think it could be misleading. That's why I'd call it a Web UI framework vs a Web Application framework. I might even call it a boilerplate UI, much like HTML5 boilerplate it a great starting point for any web app/site. In fact I use these two together often. The problem with the word boilerplate is that it can have a connotation that is negative, almost like calling something vanilla or plain. Again, it's all the context.
On Sat, Apr 21, 2012 at 2:21 PM, Dan Vega <[email protected]> wrote: > I would agree with you Ryan and for the longest time I thought the exact > same way. Then I decided to step back away from the code of a framework and > look more at the purpose. A framework gives our applications structure and > a usually a standard way for development. To me this is exactly what > Boostrap is doing. It gives me structure on the front end for my layouts in > a way that I don't have to worry about browser inconsistencies in CSS > layouts, the framework does that for me. > > I am not trying argue your point because it's a valid one. Just looking > for an open discussion on the topic :) >
