Re:The state of HTML5 for mobile app development
by kevingadd on Saturday July 09, 2011 @03:06PM
(#2746137)
He says "it’s easy to debug and make changes" when referring to mobile HTML5 development, but my experiences have been the complete opposite and the only concrete claim he makes to support this is that there's a buggy and slow tool you can use to run Web Inspector against a remote device. It doesn't even look like it has breakpoints. Am I missing some other essential tool that he assumes the reader knows about?
[ Parent
| on HN ]
Re:The state of HTML5 for mobile app development
by lukifer on Saturday July 09, 2011 @03:57PM
(#2746241)
Weinre is buggy, but it works well enough, and the web inspector does have breakpoints for Javascript. As someone who's spent way more time in web inspector than XCode, I'd say it's easier to debug, but still less powerful than XCode's tools, especially when analyzing performance and timing issues.
Re:The state of HTML5 for mobile app development
by aaronbrethorst on Saturday July 09, 2011 @03:26PM
(#2746169)
I was going to make the same comment. Frankly, I barely find gdb to be adequate for debugging iOS code (lackluster support for Obj C 2.0 properties, etc). The idea of having to debug a significant amount of JS inside of a native app shell without a real debugger gives me chills.
Re:The state of HTML5 for mobile app development
by mamp on Saturday July 09, 2011 @11:56PM
(#2746987)
The big hope is that XCode 4.2 reduces the overhead (i.e. suck less) of Objective-C through LLVM & LLDB's improved debugger, more static checking and automatic reference counting.
Re:The state of HTML5 for mobile app development
by aaronbrethorst on Sunday July 10, 2011 @01:14AM
(#2747102)
Concur, but so far I haven't seen much improvement with 4.1, which, I believe, is also using llvm by default for new projects.