mplorentz on Nostr: One of the worst parts of working on an iOS app has always been Xcode, but the past ...
One of the worst parts of working on an iOS app has always been Xcode, but the past few months it’s been even worse than usual. It’s hard to get into a flow state programming when I have to restart Xcode every 5 minutes because it stopped showing errors inline, or had an internal consistency error, the SwiftUI previews don’t work most of the time, the debugger doesn’t work with async code, etc.
I’ve been dipping my toes into VSCode (well actually VSCodium) this week trying to see if I could get it configured well enough to do most of my iOS development. It’s been hit or miss so far. Has anyone here tried this already?
Published at
2024-03-29 19:38:18Event JSON
{
"id": "d4b431a30034e2e804ac3572cef8cfe2763363072e59e6bc946dd9865863903c",
"pubkey": "d0a1ffb8761b974cec4a3be8cbcb2e96a7090dcf465ffeac839aa4ca20c9a59e",
"created_at": 1711741098,
"kind": 1,
"tags": [],
"content": "One of the worst parts of working on an iOS app has always been Xcode, but the past few months it’s been even worse than usual. It’s hard to get into a flow state programming when I have to restart Xcode every 5 minutes because it stopped showing errors inline, or had an internal consistency error, the SwiftUI previews don’t work most of the time, the debugger doesn’t work with async code, etc.\n\nI’ve been dipping my toes into VSCode (well actually VSCodium) this week trying to see if I could get it configured well enough to do most of my iOS development. It’s been hit or miss so far. Has anyone here tried this already?",
"sig": "d8a233710e58ab8166078b52120bdea0afdce44d0e72aabf3e52463d623897bcb29c7c38df8ba4de4c2217196f1a5cc5787be604fbf0a911c0ddcb6bc606caf7"
}