3 ms·
When debugging Xcode projects I 100% use the debugger - even when doing print debugging (for e.g. hard to pinpoint UI bugs) I'll use print breakpoints since you
by kalleboo 4y ago
When debugging Xcode projects I 100% use the debugger - even when doing print debugging (for e.g. hard to pinpoint UI bugs) I'll use print breakpoints since you can add/remove/edit those without recompiling/relaunching.
When using something like JavaScript or PHP where the tooling is finicky and fragile I just give up and use 100% print debugging.
- interpol_p 4y agoXcode has really great debugging, though the debugger can be slow to initialise on the first breakpoint I love that you can hit spacebar on any local variable and "QuickLook" preview it just like a file in the finder. It even renders UIViews, and previews 3D models right in the debugger. The 3D view debugger, memory graph inspector, and all the other tools are just great
- heretogetout 4y agoOnly the first breakpoint? It's glacial for me on a pretty well spec'd 2019 MBP. Every step takes several seconds as, I guess, resources or just data are pulled from my device. I still try to start with the debugger but I almost always fall back to print statements. (It's often faster to add print statements and rebuild+redeploy than wait for a step or two in the debugger).
- kalleboo 4y agoThe QuickLook is also amazing for Core Image rendering flows, where it generates a PDF showing every filter/rendering step!