I just released another blog post (it’s German) on our company blog … topic is “why am I blogging”.
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 (http://www.pixijs.com/) 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.
Some time ago I wanted to read an article about NuoDB on forbes.com. 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.