June 21, 2009
10:03
Interview of @eschnou at Google I/O
As you know, I went to San Francisco for a week in May, on invitation by Google to demo Storytlr at I/O. Here is a short interview they did during the conference. This way, you can now put a face on Storytlr (the other face, the one of Alard, is missing as he wasn't able to join me at I/O).
Comment by Pierre-Olivier Carles
on 22 Jun 09 at 9:43 CEST
Interesting points of view... specially the part when you explain that scalability is not that easy to plan :-)
Comment by blog
on 25 Jun 09 at 20:36 CEST
Hi PO, thanks for stopping by :-) Indeed, scalability is tough but our biggest mistake is not to have planned for internationalization from the start. Just adding a small library and following a few convention would have made all the difference. Today, if we want to translate, we have a huge refactoring task ahead of us. Not fun :-(
Comment by pierreoliviercarles
on 26 Jun 09 at 4:50 CEST
My pleasure... You know I love Storytlr :-)
Do you really need to translate now ? Why not keeping on going improving the service and bringing it to a even higher value for the user... and then consider internationalization later ?!? It would have been better to think about it at the very beginning... but now, as it's too late, will it make a big difference ?
PS : And by the way, may be you could fix this tiny bug-feature-breakingballs thing ? :-)
http://skitch.com/pcarles/biubu/storytlr-blog-interview-of-eschnou-at-google-i-o
Do you really need to translate now ? Why not keeping on going improving the service and bringing it to a even higher value for the user... and then consider internationalization later ?!? It would have been better to think about it at the very beginning... but now, as it's too late, will it make a big difference ?
PS : And by the way, may be you could fix this tiny bug-feature-breakingballs thing ? :-)
http://skitch.com/pcarles/biubu/storytlr-blog-interview-of-eschnou-at-google-i-o
Comment by eschnou
on 26 Jun 09 at 5:01 CEST
Ho no we don't and we are not working on it. However, if I had panned things right in the begining, today I could just ask my mother to translate the assets and it would be done.
PHP for example has excellent internationalization frameworks, but you must use them from the start.
I think that many US based projects simply don't do this. This is one reason why going international is a pain for them. Refactoring would be too costly.
PS: Thx for the bug, had actually never seen or heard complains on this. Will fix asap.
PHP for example has excellent internationalization frameworks, but you must use them from the start.
I think that many US based projects simply don't do this. This is one reason why going international is a pain for them. Refactoring would be too costly.
PS: Thx for the bug, had actually never seen or heard complains on this. Will fix asap.
Latest comments