I’m back in Karlsruhe for another few weeks (until mid of Apil). And back at my beloved old team which is now called “Web Sales Development”.
I’ll be doing some iPhone development for the next months – really excited about that! There are several exciting projects in the pipeline, too. Can’t wait to get my hands on coding again! 2010 is going to rock!
These are crazy times for me! And that’s true in many ways:
In the last months I’ve been working with three very innovative mobile development frameworks – each of which is remarkable in its own way. I’ve to hate and love all of them and I’m so thankful that I got this chance at all! I’m very happy that I did not loose touch to my old colleagues at WebDev/WebSalesDev and still see them every once in a while.
I’m also working on a very interesting project in my spare time with my buddy Lino – I hope we can give you an update about this soon.
And I’ll be back to Mosbach, soon. I’m so curious about what’s up next – crazy times everywhere I look :-)
In the meantime: I’m afraid I often don’t have the time to post new content here – and some things pass by so fast I just don’t feel like they’re necessary or that important at all.
Stay tuned!
With all the heck about Apple blocking and removing applications from the App Store there clearly are some things they don’t have a problem with:
In all the clauses of the App Store there has to be one banning mass-application-submission, doesn’t it?
Oh by the way: those “SpeedDate” apps at the moment fill about the first three pages if you sort by date so there are about 60 of them…
Some things just can’t be clear enough. Maybe that’s why Apple’s iTunes lists the current category in the App Store not only once or twice but under every single application tile:
Well… it might be convenient that apps in a certain category are all in that certain category. Just to make sure you know that :-)
By that reason those pages in the App Store containt the name of the category about 60+1 times. I call that: wasted space!
So after all Google has developed its Chrome Frame plugin for Internet Explorer for a good reason: enabling the majority of users – which are unfortunately still using Internet Explorer (6,7 AND 8) to have a better experience with HTML5-based websites.
Lars Rasmussen posted on the Google Wave Developer Blog that Wave will inform Internet Explorer users to install Chrome Frame for a better user experience. Reason being that Internet Explorer is just too slow at interpreting JavaScript and DOM Manipulations – features Wave heavily relies on. IE’s support of modern web standards such as HTML5 is pretty poor, too.
I’ve been experiencing the same issues with IE over and over for myself – yet in a smaller dimension: Every hour (and it have been many hours) a developer spends on the specific quirks on IE (which of course are different per each version) and to fix them for their application is not spent on adding cool new features or bug fixes which affect general issues.
Since this has been a problem for so a long time I hope this finally helps to fix this issue.