We really need an "open standard" for CSS classes/ids. It would be so awesome if we just could change CSS Files, to switch (i.e.) between Bootstrap and Zurb.
With CSS pre-processors like Sass, you can use semantic classes and IDs (instead of, e.g. .span-4) and extend them with the rules you need from the framework. Doing this makes switching frameworks easier, makes your markup more meaningful, and reduces network overhead as you can just send the stuff you're actually using.
I think something like Bootstrap is fine for any "web app"; working with a "standard" takes care of a lot of the details, and saves a hell of a lot of time. Maybe it's many years of Windows development, but it's kind of nice working to a Common User Interface.
i can agree to that. i think people use bootstrap etc. wrong. It's a framework to start with, not to finish your whole project without changing anything.
I agree as well - there are good for internal tools and prototypes, but absolutely not for production sites. At the same time they are useful and save a lot of time we spend repeating ourselves writing code for the same ui elements and patterns. I've been hacking on a framework like these, but that's flexible and modular, so you can break it down and customize it as much as you need. I've used this in several production websites for large companies and you wouldn't even know it was there. Working on documentation : )
Comments
We really need an "open standard" for CSS classes/ids. It would be so awesome if we just could change CSS Files, to switch (i.e.) between Bootstrap and Zurb.
With CSS pre-processors like Sass, you can use semantic classes and IDs (instead of, e.g. .span-4) and extend them with the rules you need from the framework. Doing this makes switching frameworks easier, makes your markup more meaningful, and reduces network overhead as you can just send the stuff you're actually using.
I sure hope Bootstrap doesn't become "standard".
I think something like Bootstrap is fine for any "web app"; working with a "standard" takes care of a lot of the details, and saves a hell of a lot of time. Maybe it's many years of Windows development, but it's kind of nice working to a Common User Interface.
i can agree to that. i think people use bootstrap etc. wrong. It's a framework to start with, not to finish your whole project without changing anything.
I agree as well - there are good for internal tools and prototypes, but absolutely not for production sites. At the same time they are useful and save a lot of time we spend repeating ourselves writing code for the same ui elements and patterns. I've been hacking on a framework like these, but that's flexible and modular, so you can break it down and customize it as much as you need. I've used this in several production websites for large companies and you wouldn't even know it was there. Working on documentation : )