Recorded – watch the full episode on YouTube.
WWDC20 is only a couple of months away as we record this – what are you excited about for this year?
Ellen Shapiro: I have to admit that I would love to see Combine go open source. I don't know that's going to happen. I'm really excited to see the second version of SwiftUI. I have to admit, I haven't gotten as much time to play around with it as I would like to. Because I've mostly been working on under the hood stuff with Apollo. But it's been really exciting to see how much easier it has the potential to make building and iterating on screens for a lot of people. I'm really excited to see what people are coming up with.
And honestly, I think this year I would just be really happy if we could have a Snow Leopard release. Just fix everything! Take all the stuff that's been happening and fix it. I will admit like the one thing that will get me to like jump off my couch and go “ahhh” is real plugins for Xcode. I don't think it's going to happen, but prove me wrong Apple.
“Honestly, I think this year I would just be really happy if we could have, everybody jokes about, a Snow Leopard release. Just fix everything!”
Paul Hudson: I thought last year would be the year. They're finally seeing sense, but arguing so much about this. And I still think this year is going to be the year. I'm an eternal optimist. I'm convinced this year, we're finally going to see Xcode with real extensions or plugins in there to do the old Alcatraz-style stuff.
Ellen Shapiro: That would be really nice. I think it is something where people who are using Swift use Visual Studio, more for server side stuff, are really starting to see, Oh, having a real plug-in architecture for your IDE is super helpful.
It would be really nice if that happened. I am certainly not putting any money on it. But it would be really nice. It's definitely something that would be helpful. My pie in the sky wish is some version of XCUITest that doesn't run in a separate process. That's one thing that drives me absolutely bananas about XCUI is that you can't make any changes to your application under test. You can't mock out what the data is. I used to work for a parking app and we needed to test, “hey, if I make a reservation from December 31st of one year to January 1st of the next year,” that that actually works.
And you couldn't do that except on December 31st without doing a whole bunch of weird workarounds with XCUI. Whereas there are other UI testing frameworks, like Kif that run in process and are able to take advantage of mocking and things like that. And dependency injection in ways that is really a lot harder to do with XCUI at least in a way that doesn't involve putting test code in your production application. Which I am not a huge fan of.
This transcript was recorded as part of Swiftly Speaking. You can watch the full original episode on YouTube, or subscribe to the audio version on Apple Podcasts.
SPONSORED Learn the most up-to-date techniques and strategies for testing new and legacy Swift code in this free practical course for iOS devs who want to become complete Senior iOS Developers.
Link copied to your pasteboard.