3 ms·
Well I do it. Or did till App Code was killed. I still do some Swift in CLion. Here’s my reasons: - Xcode has many failure cases for refactoring or is slow at
by dagmx 4y ago
Well I do it. Or did till App Code was killed. I still do some Swift in CLion.
Here’s my reasons:
- Xcode has many failure cases for refactoring or is slow at finding symbols across extensions. Jetbrains handled it effortlessly. God forbid something crosses a target boundary.
- Xcode is really terrible for multi language projects. If you’re sticking to ObjC and Swift, it’s fine, but the C++ support is really poor. If you need to throw in Python or anything else, good luck. Jetbrains handle multi language super well.
- extensibility is a big deal. Xcode isn’t extensible (well only in a very limited way) and there’s many plug-ins that I either use or create for myself to speed up my work.
If Xcode supported LSPs, it would honestly change the equation greatly. But today myself, and several other devs I know, edit outside Xcode and build via the command line tools instead.
- marcellus23 4y agoFair enough. My point wasn't that literally no one does it, but more that it's pretty uncommon. You can't get live errors/warnings in Swift or ObjC outside of Xcode, right?
- dagmx 4y agoyou can since those are a property of clang itself not Xcode. Xcode does some analysis on top of clang but you can use clangd in an LSP. What you leave behind though are any of the interactive bits like live previews, storyboards, all the core data utilities.
- pjmlp 4y agoTo be fair Objective-C and Swift are really the languages Apple wants everyone to use. C++ official support in OS frameworks relates to IO and Driver Kit, LLVM and Metal Shading Language. Whatever works for Objective-C also works for C.