Category Archives: vraagje

blogposts op blog.futtta.be waarin ik mijn lezers nederig om hulp vraag (where I ask my readers to teach me)

Now you CNAME now you can’t

Yesterday at work I had a discussion with one of the guys in charge of our DNS. I asked him to create a CNAME record on one of the domains under our authority, pointing to an external canonical name, but he kindly refused. So I asked whether this was company policy of some kind, as I saw no technical reasons for this not to work, but he answered:

No, the problem is technical; the hostname one points to, has to be managed on the same DNS-platform and this can’t be done in this case as we’re not the SOA for the external domain

So to prove my point (yeah, that’s how I roll) I created a temporary CNAME-record on my own domain, pointing to the external hostname (much the same way static-cdn.futtta.be is just an alias for blog.futtta.netdna-cdn.com) but that did not convince my colleague either:

Making a SOA on a server where that isn’t allowed, is not really according to the standards.

As the change was pretty urgent and there weren’t any important downsides, I adapted my change request for the DNS-entry to be created as an A-record. But in the mean time I started reading up on CNAME’s on Wikipedia and glanced over the two relevant RFC’s (RFC 1034 and RFC 2181), but I really can’t find any confirmation of what my (respected) colleague is referring to. But I’m sure there are smarter people reading this here blogpost who might be able to explain what I am obviously missing, no?

WP YouTube Lyte on Android: native or in-browser playback?

With the latest release of WP YouTube Lyte I fixed a problem where iOS users had to click twice to view a LYTE-embedded video; once to activate the iOS YouTube player and once to start the actual playing. On Android that problem does not exist, as LYTE embeds can be played inline in the browser.

Based on my own tests however, performance and quality aren’t always optimal when compared to the experience the native YouTube app provides. So now I’m wondering; wouldn’t it be better to not only detect iOS, but also Android and have both of them play in their respective a native players, even if on Android this isn’t an absolute requirement?

Advantages:

  1. better video playback performance/ quality
  2. somehow feels more professional (it’s the way the YouTube mobile site seems to work as well for example)

Disadvantages:

  1. you force visitors out of the context of your webpage
  2. a small percentage of Android visitors will get an ugly error message as they do not have a native YouTube player
  3. only works for single video’s, not for playlists (or at least so it seems) and the audio-only trick obviously won’t work either

What do you think? Speak now or be silent forever!

And let me throw in a vid (Spiritualized with “Hey Jane” live) just for the heck of it;

Spiritualized – Hey Jane (live @ Maida Vale for BBC 6 Music)

Watch this video on YouTube.

And if you’re on Android you can click here to trigger the YouTube app to see the exact same thing.

Wie is haar ei kwijt?

Ge maakt wat mee als ge kippen op den erf hebt lopen; de ene dag komt  een egel uw kiekens aanvallen, een tijdje later ligt er een vreemd ei in de nest:

Nu is de vraag: welke vogel dacht hier koekoek te zijn? Een echt koekoeksei is het waarschijnlijk niet; als ik Wikipedia mag geloven leggen die begin juni hun ei bij zowat alles behalve kippen. Op Facebook opperden vriendjes dat het een merel- (maar die hebben blauwe eikes) of kievitsei (maar die zijn donkerder, met grotere vlekken) kon zijn, maar we zijn er dus nog niet uit. Wie helpt deze vondeling uit z’n slepende identiteitscrisis?

spring + groovy + grails = ?

Just read that Springsource (“Weapons for the War on Java Complexity”!), Rod Johnson’s company, has acquired g2one, the company behind Groovy and Grails. Looks like there’ll be 2 major Java development stacks; all things JSR/J2EE on one hand and Spring/Groovy/Grails on the other? What train should one hop onto, when having to choose a new web development framework?

Après le N-VA; débarrassons nous du FDF?

Une question pour mes amis et collègues Belgo-francophones:

Comme le N-VA de Bart De Wever ne fait plus partie du Gouvernement Flamand et que Geert Bourgeois ne sera donc pas dans la délégation Flamande pour le dialogue communautaire, n’est-il pas le moment idéal pour se débarrasser aussi de Olivier Maingain et son FDF, enfin de maximaliser nos possibilités de succès?

Merci d’avance pour ce geste politique courageux et indicatrice de votre souhait de réussite!

wanted; maingain et de wever by zattevrienden.be

Firefox 3rc1 shines in Javascript benchmark

blazing firefox3As the official release of Firefox 3 is getting closer, with Release Candidate 1 being available since May 17th, I decided to boldly go where codinghorror has gone before and do a quick-and-dirty Javascript-performance comparison of the different browsers I’ve got installed on my Dell Latitude D620 laptop, using Webkit’s Sunspider benchmark.

Let’s start with the results for the browsers on my Windows XP SP2 installation, ordered from slowest to fastest. Each test was executed 2 times, clicking on the results will teleport you to the detailed results where you can paste the URL’s of another test to compare.

The MSIE7-results are probably not entirely representative, as I use Tredosoft’s standalone IE7. This is a bit of a hack to have IE7 on my otherwise MSIE6-based system. Moreover my corporate Windows-installation is infested with crapware, notably McAfee OAS and Zonealarm seem to be slowing things down enormously. The codinghorror-tests indeed show significantly better results for this browser, although IE does have serious issues with string concatenation, which should be fixed in IE8.

On the same hardware, but booting in Ubuntu 8.04 (Linux) form my external USB HD (a.k.a. my ‘disktop‘), I got the following results:

Firefox 3 RC1 seems slightly slower then b5, but maybe the Ubuntu-b5-version is compiled with optimizations? Firefox is also faster on Ubuntu, but the anti-virus-bloat is probably messing with our heads here (although Opera is slower on Linux, go figure).

The general conclusion however; Firefox 3 is a huge step forward as far Javascript-performance is concerned. Users of javascript-heavy web-applications such as Gmail, Google Reader, Zoho Office and Zimbra should benefit enormously from this. It would however be very interesting to perform similar tests with regards to ‘normal page rendering’ (html/css). Does anyone know of such benchmarks?