Re: Poor Web Development
Really the frameworks are supposed to be for prototyping, then when you're done working out what you need you start cutting out the bits you don't. jQuery introduced subcomponents so you can load individual parts rather than the whole thing and, according to them at least, the full version will drop to 11kb when minified and gzipped during transfer if you use the minified version. jQuery UI lets you do custom builds which only include the features you want. Twitter Bootstrap you can just remove the js entirely if you aren't using it, and I'm sure other libraries like this let you pick and choose what parts you actually want
Problem is this requires people to keep it in mind when they're building it, and plan time into the project for doing clean up work. There's also the issue of third party services, like the Twitter API or ad networks (mentioned in the article), where your page load time is impacted by the response time of third party servers which you have no control over. Not to mention if you have a lot of files to download rather than a small number of combined ones the overheads from the http requests will slow things down
So yeah, all in all there are ways to improve it, but they depend on better planning of projects and getting clients to understand that more shiny doesn't necessarily mean more sales
Biting the hand that feeds IT
