4 ms·
Good point. By 'best tooling' I'm mainly thinking about two things: - How easily can I debug things if something breaks? - In case I'm not happy with a certai
by DeepDuh 14y ago
Good point. By 'best tooling' I'm mainly thinking about two things:
- How easily can I debug things if something breaks?
- In case I'm not happy with a certain behavior is it a dead end or can I simply swap out a parameter / function / module (in that order)?
These two aspects are IMO essential for choosing any development environment if I have the choice. This goes for web development too, which is why I'd prefer something like Django over something like Joomla for example. I don't even care so much about performance at that point.
Do you agree with me that at least in case of iOS, native beats html+js+webviews in those two points?
- svachalek 14y agoI wouldn't. Debugging js is quite easy, overall probably more straightforward than dealing with Xcode. And there are tons more choices in the js world, having both more developers and a more free-as-in-speech mindset. The big downside is the one Facebook found, js in a webview is just... slow.
- jim_kaiser 14y agoCorrection. Debugging JS in not easy. I have been working on a native application which has some HTML5 components in webviews. There is no easy way in XCode to debug JS in this kind of mixed application. In fact, it is a royal pain in the ass. You can run the JS in Chrome debugger or a web development IDE, but that can only work if all your functionality is in HTML5/JS and not a mix of Native and HTML5.
- DeepDuh 14y agoThanks. I was gonna ask parent how he does it because if it's easy for him he might know some magic I'm not aware of.