I’m not a framework user, to me the benefits of rapid prototyping are outweighed by the amount of code I have to strip out to make something acceptable for final release.
I’ve wanted to embrace a good HTML/CSS framework since they first started popping up last year and despite a lot of seemingly good options around there for rapid prototyping in the browser, I can’t help but feel there’s still a large gap between the code used for rapid prototyping in the browser that comes from a framework like Bootstrap and the bloat that I’d still consider unacceptable in optimised final release code.
Typically I don’t use a framework beyond some basic home rolled styles but looking at Jetstrap this morning I thought I was seeing a real game changer and it’s certainly a clever bit of kit but looking at what was output in the HTML & CSS beyond the speed of creation, it wasn’t code I’d be happy to deploy. There was just too much of it.
Nobody likes repeating work and I’m sure we all strive to create code that adheres to DRY principles so I’m still struggling a little to connect the benefit of rapid prototyping using these tools but then ending up with code I would either throw away once it’s been shown to a client or something I then have to go back and hack out loads of divs and markup so it’s suitable for a final release.
I’m going to hope I’m not the only one in the world who’s not using a framework for these reasons but I’d love to hear others experiences and reasons for not fully embracing frameworks and I guess the question I’m asking is do you:
- Make use of heavier code bases in order to prototype quickly in browsers but deploy less than optimal code in the final product?
- Make use of heavier code to prototype, then spend time stripping out unnecessary code ready to release?
- Not use frameworks and prototype using simpler, custom HTML & CSS which is then leaner and closer to optimal?
- Some other mixture or method?