3 ms·
I'm one of the Cappuccino developers. While this is neat, it's not particularly surprising, and it misses "the big picture", not unlike the sort of "MapReduce i
by tlrobinson 18y ago
I'm one of the Cappuccino developers. While this is neat, it's not particularly surprising, and it misses "the big picture", not unlike the sort of "MapReduce implemented in 10 lines of Ruby!" posts we see so often.
It actually highlights several of the reasons we set out to do Cappuccino in the first place (some of which might be offensive to web developers):
1. This is minor, but the speed comparison is a little unfair, since the original has 3 times as many photos to scale. Yes, Objective-J method calls have a little bit of overhead, but in profiling a real world application (280 Slides), the message dispatch overhead is not a bottleneck (something like 1%).
2. It's 45 lines of JavaScript... plus several hundred lines of CSS. With Cappuccino you don't have to write CSS, ever. Some may see this as a disadvantage, but we don't. No more fiddling with CSS hacks to get it to look right in all the major browsers, which brings me to my next point.
3. It doesn't work correctly in at least Firefox 2 (OS X) and IE. Yes, this could be fixed, but it's another thing you (theoretically, and usually practically) don't need to worry about when developing in Cappuccino.
4. Cappuccino is designed to scale. The FlickrDemo is a small demo which is just that, a demo. It's definitely on the small side of the types of applications Cappuccino is good for. I'm not bashing jQuery, but I'm honestly curious if anyone can point me to an application written in jQuery approaching the complexity of 280 Slides.
- deleted 18y ago[deleted]