Apple event 2014-09

I’m kind of a fan-guy. Apple stuff is really interesting and especially the latest iOS/iPhone version really seemed to be a good release again – something you don’t wanna make jokes about like “oh – they added a new icon row” … So I sat down on 09-09 and wanted to watch the live event … unfortunately I got this:

2014-09-AppleCountdownUhm – seems like a normal countdown? Be happy! Cheer! It’s starting now! … … … Nope … … … It’s all about the little sentence below the “add to your calendar icon” … it reads:

“Live streaming video requires Safari 5.1.10 or later on OS X v10.6.8 or later; Safari on iOS 6.0 or later.”

Come on! I’m on a Chrome – Webkit – that HAS to be sufficient … Nope … no Apple guy (my Mac-Mini is in a drawer, but I don’t wanna unpack it and my Apple TV Remote is hidden somewhere between some other parts) … but – hey! You can’t just lock out your fans, because they’ve got other devices as well. That’s really not nice.

I still watched the stream … Some guys showed it, but made comments about everything, Stating every X minutes that “you could switch to the live-stream, if you didn’t want to listen to them” … o0 … yeah… well …


I recently searched for a 2D-Javascript game engine and came by this site: It lists various game engines. It seems their default sorting is “by popularity”. So let’s have a look at the first four entries. Construct 2 is a “whole editor, bring everything and just click your logic”-framework. I saw a screencast some days ago about it. It’s really cool for guys that don’t wanna do it “themselves” 😀 (no offense – it’s just to heavy-weight for me). Impact has a 99$ fee I didn’t want to pay at startup and EaselJS looks really cool, but was to much for me to start with (It’s part of CreateJS and that one brings sound, tweening and even a separate preloader). So I decided for PixiJS (after two colleagues, which used that one as well, told me it was a good lib).

Fun-fact: If you sort the list by “rating”, you’ll get pixi at the top ;-).

While some of the other frameworks bring “all you need” to the party, Pixi ( just focuses on the rendering. They claim to be “the fastest” … that’s a good slogan, which I’ve already read several times, but if you read the discussions in the forum of Pixi, they’re always consider things like “we could do that, but that’s slower – we should go without that”.

Unfortunately the reason I read this was because I searched for shaders. I was told that they’re just gonna enable shaders for WebGL, but not for the canvas fallback (because Canvas doesn’t support them and they’d have to re-implement that behavior themselves). Even though they’re normally “It wouldn’t work in both ways, so we don’t implement it”, they seem to make an exception for the shaders, so you can use them if you’re really sure. In the documentation (which is a minus point, because it’s not really good maintained, but there’re several example projects where you can take the information from), you can see that it’s just offered for that one case and you won’t get the same functionality in the fallback if you’d use that feature.

As I tried to figure out whether I want to use Pixi, I just had written some custom clearRect logic for my own canvas script. So I wanted to check how the redraws in Pixi were handled … while I just re-rendered the area I wanted to change, Pixi always refreshes the whole area (you can see that in the chrome-dev-tools (F12 -> rendering -> Show paint rectangles).

I guessed it wouldn’t be that nice to have that behavior and so I searched for performance measurements of Pixi … and they all said: If you use WebGL, your performance will keep up … if you go to the fallback x00 (think it was about 600) items will tear down your framerate.

So I decided to stay with Pixi for the moment … and if I should realize at any time, that Pixi is not as good as I currently hope, the object model will save me … you just modify existing objects and the render-loop of pixi redraws them. So If I’m required to replace Pixi, my model will already be nice and clean so that it shouldn’t be a big deal.

Login Usability

Some time ago I wanted to read an article about NuoDB on Was interesting to read, but I didn’t fully comply with the authors opinion. So I wanted to ask in a comment about something I heard on a conference in Hamburg. But that’s just a side-story.

The funny thing happened, as I wanted to comment. Of course you’ll have to create an account to comment to minimize spam. But because I haven’t an account, I created one … After that was done and the account activated, I wanted to post my comment … unfortunately while the page still told me I wasn’t logged in and wouldn’t let me post, the login frame itself recognized my just activated account and told me – you can’t login … YOU ARE ALREADY LOGGED IN … o0 …


What the hell? Why can’t you just check if there’s a user after clicking the “log in” button instead of telling me I was not permitted, because I already did that. Reloading the whole page fixed the problem.

That’s a good example why you (and I) always should think about the usability while developing new stuff.

Many new beginnings

Phew! A new beginning every … I don’t know … two to three years?

My old blog was based on BlogEngine.NET and it worked very well, but maintaining it bilingual was quite time consuming. So after some blog posts, the rate of new ones decreased continuously. Then we (Chris and I) tried to start something new, but good things sometimes last a bit 😉 – perhaps we’ll see something there in a few weeks. But to get something going now, I decided to give WordPress another try.

While I’m typing that text I produce lots of red underlines below every single word, because my browser is set to German and sometimes just changes the words while I’m typing, but somehow I feel more comfortable entering the text directly in here instead of Word … don’t know why – just a feeling. Perhaps because of the fancy controls on both sites, so I feel more important 😉 .

So I’d be happy if you’d come back from time to time to check for some new posts. I’ll keep writing my bigger posts for our company blog ( in German, but sometimes there’re things that do not match this other blog. Besides that there might be topics I want to tell my opinion about without ensuring it’s the companies opinion as well – that stuff will be posted here as well.

Thanks for reading.

See ya soon (*hopefully* 😀 )