A post from iphone app
Sunday, August 10th, 2008 | Personal | No Comments
I downloaded the wordpresd iPhone app couple days ago and finally started to use it. So far so good 
Matt Harding visited Yahoo! campus
Saturday, August 9th, 2008 | Personal | No Comments
I came to a blog that I saw Matt Harding visited Yahoo! campus up in Sunnyvale and made a video clip with yahoos. I am very positive that almost all web users who already saw his video would like him a lot as being inspirational.
Anyways, here’s the url where you can go to and watch Matt’s video with Yahoo!
Flash Player 9 April Security Update
Wednesday, March 19th, 2008 | News | No Comments
Flash Player Bug List
Wednesday, March 12th, 2008 | Flash | AS2, 3 | No Comments
Title says all.
It’s a really good reference to have when you are working with flash all the time…
live.yahoo.com
Wednesday, February 13th, 2008 | News | No Comments
I don’t know when this went live, but live.yahoo.com is live now.
It is a totally interesting and experimental site.
Perhaps next step would be to add more of social network feature??
Comment on “A Study of Ajax Performance Issues”
Tuesday, January 29th, 2008 | Ajax, Client-side, Tips | No Comments
This study shows performance issues of native javascript APIs on multiple browsers.
I think this is definitely a good read for all DOMers who work closely with client scripts.
I just want to point out couple things.
1. innerHTML vs. appendChild(dom)
I use innerHTML when I do not need to get a reference back for later use from the operation or generate many HTML elements. When I need to manipulate the HTML element that is created through DOM object, I usually cache the object to a global variable or a object’s property. Also when many elements need to get appended to a DIV tag or something else, innerHTML gives faster performance over appendChild method. If you look at the tv.yahoo.com/listings_setup page, channel rows are created through innerHTML and it’s quite quickly rendered even if there are over 500 rows. If I injected more than 500 rows using appendChild way, it would have been very slow and eventually locked up a browser for a bit during the process.
2. Let’s not focus on numbers too much.
It’s good to know the detail number of each process. However, even if one process took 30 or 100 milli seconds, it would have not been noticed by a regular user. If one tasks got involved with multiple procedures and ended up taking up 1-2 seconds, I’d call it “design problem”, not a performance problem. With DHTML manipulation and Ajax, possible things you can do with them seem endless, but you do not want to push the line too hard. Especially in ajax application, design/architecture matters more than API/scripting.
3. Learn the limit.
Knowing the limit is very important. There are limits in any scripting languages. The role as a developer/engineer is to play around the limit and still produce a nice product for users. Of course, there will be requirements from product people that may hit the limit and cause performance issue, but as a developer/engineer you should put your efforts to change the requirements or be creative to do workaround on the limit.
Again, the numbers on the report give a real nice overview of what API to use and not.
Archive
- August 2008
- March 2008
- February 2008
- January 2008
- November 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- February 2007
- January 2007
- November 2006
- October 2006
- September 2006
- June 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
- April 2005
- March 2005
- February 2005
- January 2005
- December 2004
- November 2004
- October 2004
- September 2004
- August 2004
- July 2004
- June 2004
- May 2004
- April 2004
- March 2004
- February 2004
- January 2004
- December 2003
- July 2003
- May 2003