- ViaboxxSoftware Developer, 2011 - present
- IP Labs GmbH (FujiFilm Group)Software Developer, 2009 - 2011
- Objectware AS (Itera Consulting)Consultant, 2006 - 2009
- Primetime AS
The problem is that while these frameworks do make it easier (and faster) to code, you are only using a fraction of the code. The result is bloatware in which your site ends up being terribly slow.
And I see this with so many sites. Look at the example below. It a page speed test from one our our national newspapers, loading just one page (this one: http://goo.gl/m9xurD)
The page itself is nothing special. Sure, it contains a lot of images and links, just like any other page on a newspaper site, but there is no super fancy interactivity. It's very basic stuff.
The result of this is that the page loads rather slow, of which 69% is due to the scripts alone. The total size of the scripts are 0.7 MB + another 0.6 MB for other elements that couldn't be identified.
And, of the total size of the page (which is a staggering 2.2MB) more than half is coming from non-page sources.
To put into perspective just how much code this page is including, think of it like this:
- 552,620 characters long
- 79,445 words long
(Harry Potter and the Philosopher's Stone was 76,944 words long)
I see this problem on so many sites. Web designers have become lazy (or too busy). Instead of thinking about what frameworks they use, they just keep adding them. And of those frameworks added, they often only use 1% of what the code is designed to do. Often most of the functionality is only needed on a very few pages but are included on every single page.
"Topics that have been cooking in 'next' for 2.0 have been merged to 'master', which means we are committed to make the next one a big release. Kind of scary, isn't it?"
According to the git log, he merged the changes to his local master branch four days ago, but pushed it to the main repository at git://git.kernel.org/pub/scm/git/git.git just a few hours ago.
If you're up for some local testing, get yourself a clone, compile and test out all the newest changes that will appear in 2.0. The master branch from git.git is considered stable, all commits there have gone through some rigorous testing before they're even considered ready for master.
You can read more about the upcoming changes at the link below.
GitHub still hasn't caught up :)
Git v1.7.9 Release Notes ======================== Updates since v1 ...
Git v1.7.9 Release Notes ======================== Updates since v1.7.8 -------------------- * gitk updates accumulated since early 2011. * g
Podcasts for Programmers - Thomas Ferris Nicolaisen
tfnico's (Thomas Ferris Nicolaisen) home on the web.
Being The Worst | Adventures in Practical Software Design
This episode is the third of a three part series on client-side development. Kerry and Rinat discuss their initial experiment with applying
Download Wrappers and Unwanted Software are pure evil - Scott Hanselman
Scott Hanselman on Programming, User Experience, The Zen of Computers and Life in General