3 ms·
Even on MacOS. I was playing with XCode recently (I don't normally do Mac development as such even though I use Macs as my primary computers) and was disappoint
by jhbadger 2y ago
Even on MacOS. I was playing with XCode recently (I don't normally do Mac development as such even though I use Macs as my primary computers) and was disappointed to see that they've gotten rid of Interface Builder as far as I can tell, as that was one of the greatest things modern MacOS inherited from NextStep.
- fzzzy 2y agoInterface Builder has just been integrated into Xcode for a very long time now.
- jhbadger 2y agoI don't claim to be an expert on Xcode but when I was playing with Xcode 15 the UI editor seemed nothing like Interface Builder -- not only from NextStep but even from earlier versions of Xcode.
- robinsonrc 2y agoYou may have been working in a SwiftUI project which does things differently from the older IB ways
- karmakaze 2y agoInterface Builder was the coolest thing, especially its struts-n-springs-constraints. Xcode is in contrast among the worst visual builder I've used, everything feels so tedious. (AutoLayout is the real thing and Xcode's UI feels 2nd class.) Did they also get rid of those connections between code and widgets? That would make sense as it's such a lone mechanism to be foreign to most now.
- galad87 2y agoStruts-n-springs-constraints and outlets are still available.
- jwells89 2y agoI wish it hadn’t been. It’s been considerably more slow and buggy ever since the merge. Pre-merge I loved using it, but post-merge I avoid it in favor of code, except for Mac projects which is where it’s least buggy.
- ryukoposting 2y agoI guess I'm too young to understand the phrase "Even on MacOS" here, as the developer experience I personally know on MacOS is worse than the one on Windows in a variety of ways, and it's not a high bar.