-webkit isn’t breaking the web. The W3C is

February 14, 2012 § Leave a comment

In the post Webkit isn’t breaking the web, you are, Scott Gilbertson intimates that it is the developers that are leading us to a new era of browser-wars by only implementing the -webkit prefixed CSS properties. The notion is that Webkit currently dominates the mobile browser market, so much so that other browser vendors are considering implementing the -webkit prefix. I view it differently. I place the blame squarely at the feet of the W3C.

« Read the rest of this entry »

CoffeeScript is Afrikaans Javascript

February 7, 2012 § 16 Comments

A while ago I met a few Afrikaans speaking people, and found out that (being Dutch) I was able to understand them pretty well, despite the fact they were speaking Afrikaans.

Afrikaans is one of the newest West Germanic languages in the world and is primarily spoken in South Africa and Namibia.
The Dutch commander Jan van Riebeeck founded a new colony in 1652 near today’s Cape Town. Since then the Dutch language that the inhabitants spoke started to evolve and developed itself into a new language. This happened because of the influences of other languages that were spoken in South Africa at that time. About 90-95 percent of the Afrikaans vocabulary is of Dutch origin. The other 5-10 percent is copied from languages like Malay, Portuguese, Bantu and Khoisan. Which were the native languages of the inhabitants that were moved to South Africa by the Dutch. It was not until 1925 that Afrikaans was acknowledged as an official language. Before that it was considered to be “kitchen language” for the unlearned and not suitable for use in authorities like government, church and court.

« Read the rest of this entry »

Monitoring a site after launch (part 1)

February 6, 2012 § Leave a comment

A lot of effort goes into launching a project, but often they can be found neglected after launch. We see this more in client projects with a launch date, than with start-ups or any of our internal proprierty work, but the ideas here should apply to all.

It is niave at best, to assume that once launched the project is done – to this end we always encourage clients to budget for work *after* launch. Sometimes this can be a hard sell, because people assume that once something is launched it is done, however argubly this is the most important work to be done. Before launch you are essentially working on educated guesses and experience (or hopefully user testing), but after launch you can see how real users interact with your work and even ask them for feedback.

« Read the rest of this entry »

Where Am I?

You are currently viewing the archives for February, 2012 at Logical Friday.

Follow

Get every new post delivered to your Inbox.