|
Most of my errors are syntax errors, not programming errors, and indeed they are annoying in WebKit/Safari/Chrome. Firefox will sometimes give me the line, sometimes it won't. The named methods and profiling do indeed work well (I wouldn't lump profiling under debugging though.) There are plenty of globals, but they are intentional. If there are a few strays becoming global, they are bugs we'd be happy to fix. In user code, the global situation is actually slightly better than vanilla JS because we give any top level vars file level scope rather than global scope. Yeah, I'm talking about my code, not yours :) But even if its true, if a 5-10% performance hit on a critical loop is important, there's nothing stopping you from grabbing the method implementation and calling it directly, completely negating any potential performance hit. Right, that's what I do, just like in Obj-C/C. And I'm definitely not going to argue about the performance of Cappuccino as a whole. I find it to be the best performing browser GUI framework. edit: I use the profiler in Chromium, if that matters. :] |