4 ms·
It's not any better on the Mac. I started trying out Playgrounds on an iPad and wondered why none of the suggestions and blogs on the web worked, only to find o
by simonh 5y ago
It's not any better on the Mac. I started trying out Playgrounds on an iPad and wondered why none of the suggestions and blogs on the web worked, only to find out there's a MAcOS version of Playgrounds and thy don't work quite the same. Then I find out there's a Playgrounds feature in Xcode and actually a lot of the guides and Stack Overflow answers are actually for that, although most such resources don't say which one they're for.
I finally settle on using the XCode one as most resources seems to be fort that, but after a whole afternoon failing to get a Playground to load a single package from Github I just flat out gave up. Pretty much nothing I could find about any of this ever actually worked.
My heart goes out to anyone trying out coding with playgrounds for the first time on an iPad and trying to find out anything useful, not realising almost all of the info they find is for the wrong Playgrounds. Compared to the built-in guides and helpful info for Pythonista and Codea it's an embarrassment.
- kitsunesoba 5y agoTo be fair, Playgrounds for iPad is brand new while Xcode has had playgrounds since Swift was released. Additionally, the Xcode feature has seen quite a lot of change in the last release or two of Xcode in effort to make it more capable. The biggest issue here is really just lack of up to date tutorials from Apple.
- bluedino 5y agoIf you can figure out how to wire up objects in the current version of Xcode and know whichever method of garbage collection they last settled on, you can still write a Mac app like it's 2003