Adam

@ryanbooker@mastodon.social @schwa@mastodon.social poor swift compiler already works so hard

@lightbeaminsight@mastodon.social @ctietze@mastodon.social yeah that all makes sense to me given my current explorations. I have an app in mind where I might do all the forms and entry native in each. But there’s at least one surface it might make sense to custom render.

@tonyarnold @AshtonDev @rudrank time to use an editor with an LSP and load modules within packages 😎

@AshtonDev @rudrank ah yeah, that sounds neat. I wonder if that’s more some incremental build limitations of xcodebuild though. Makes me want to build a Tuist skill 😂 Using an Xcode MCP would be a little limiting for me I think since I’m trying to do some parallel stuff. E.g. it can churn away on a separate git work tree while I’m doing something else

@AshtonDev @rudrank is an xcode mcp providing benefit over xcodebuild and related tools for you? Or still at the testing phase? I am finding myself running without Xcode until I need to test and make changes. But I work across a couple projects so it might be of a different workflow

@johnsundell @JamesTech they’re back! ❤️

@ghalldev this sounds relatable to me. If you figure anything else please post about it 😅 Or maybe each one is a special case about how to make it effortless I often have more success crafting an environment to succeed. Rather than tracking how often I succeed

@groue I also recently wrapped a collection view. The more modern APIs made it a joy to integrate it in around ~100 lines of view representable. The fact you don’t even need a view controller anymore was a nice surprise.