4 ms·

Is it possible that bootstrap was really only designed to "bootstrap" the design of a web project? I think that eventually the project will mature into its own.

Is it possible that bootstrap was really only designed to "bootstrap" the design of a web project? I think that eventually the project will mature into its own. I would not expect a mature project to ever "upgrade" to a new version of bootstrap as that doesn't really make sense to me.

sopooneo 14y ago
I have wondered the same thing all along. And whenever I complain about the non-semantic nature of bootstrap use, people justify with that same, "but this is just to get started" argument. So that's what everyone says. But I don't think it's what anyone actually does.
- daigoba66 14y ago
  I think if semantic markup is important, then don't use bootstrap. Once you use it, bootstrap will always be part of the project's DNA unless you do a true rewrite. But, to your point, that almost nevers happens.
jawerty 14y ago
However, at the same time a bootstrap lays the framework for a project and the stronger a framework is the easier it is to build off of it. Creating a new version of a bootstrap is to allow developing to be easier in the long run.
kev009 14y ago
Why? If I'm putting out a C++ app on Qt, surely I'll upgrade occasionally to squash bugs, improve platform integration, and use new toolkit features to make my new application features. Just because my application now gains traction, I wouldn't throw out or fork the GUI toolkit. Maybe add some extensions and helper libs, maybe throw some patches upstream, but not NIH the whole thing. Passing a common maintenance burden off to FOSS is a glorious win. When you fully appreciate Bootstrap, you'll see that's what it does.
- daigoba66 14y ago
  It guess it depends on whether you consider bootstrap a framework or a template. I know the bootstrap website banner uses the word "framework", but I definitely consider it a template.

4 ms·

Is it possible that bootstrap was really only designed to "bootstrap" the design of a web project? I think that eventually the project will mature into its own.

by daigoba66 14y ago

sopooneo 14y ago
I have wondered the same thing all along. And whenever I complain about the non-semantic nature of bootstrap use, people justify with that same, "but this is just to get started" argument. So that's what everyone says. But I don't think it's what anyone actually does.
- daigoba66 14y ago
  I think if semantic markup is important, then don't use bootstrap. Once you use it, bootstrap will always be part of the project's DNA unless you do a true rewrite. But, to your point, that almost nevers happens.
jawerty 14y ago
However, at the same time a bootstrap lays the framework for a project and the stronger a framework is the easier it is to build off of it. Creating a new version of a bootstrap is to allow developing to be easier in the long run.
kev009 14y ago
Why? If I'm putting out a C++ app on Qt, surely I'll upgrade occasionally to squash bugs, improve platform integration, and use new toolkit features to make my new application features. Just because my application now gains traction, I wouldn't throw out or fork the GUI toolkit. Maybe add some extensions and helper libs, maybe throw some patches upstream, but not NIH the whole thing. Passing a common maintenance burden off to FOSS is a glorious win. When you fully appreciate Bootstrap, you'll see that's what it does.
- daigoba66 14y ago
  It guess it depends on whether you consider bootstrap a framework or a template. I know the bootstrap website banner uses the word "framework", but I definitely consider it a template.