Ok to elaborate a little, I love my old 17” MBP. But it’s dual core, and I have a 15” a few years younger that is quad core. To do anything on the 17” with Xcode 7 (and the previous version) is basically impossible. While I could get the 15” to run it smoothly, I quickly exceeded what I wanted to do in Xcode with playgrounds. If you want to learn Swift for example, and you want to play with some basic functions, it might work out well, but if you want to play with views and controllers and models and make something, then it quickly becomes a waste of time IMHO. If you look at the WWDC ’15 vids, I think they realize it too, and you may find as I did that they are kind of pitching playgrounds at this point as a learning experience. So perhaps if you’re learning Swift or you are an educator you may find playgrounds very useful. But if you’re making apps and trying to make money it’s not worth your time, again, IMHO.
As for Swift 2.0, and Xcode 7 beta, I love them both. I am actively working to finish an app that is in Swift with Xcode 6.3.2 and migrating it daily into the other MBP with Xcode 7 beta every night just to stay on top of the latest and greatest. I expect we will launch our app prior to the Fall and iOS9 and don’t want to be hindered by the beta and 2.0 being the final product, as in previous betas you could not pass review if it was produced in beta. Xcode 7 and Swift 2 have been the most stable versions of betas I’ve seen thus far but my Apple experience has only been from Xcode 5 and Obj-C and quickly Switched to Swift because of my past experiences with Java and Swift was simply more enjoyable to work with. Hope that helps. > On Jun 26, 2015, at 3:08 PM, Fritz Anderson <[email protected]> wrote: > > I am always glad to hear how others made peace with their frustrations. > > I also hope for a substantive answer to my technical question. Any offers? > > “What do you expect from a beta” may be the only answer, but apparently most > other people don’t have this problem, so I have hopes. > > — F > > > On 26 Jun 2015, at 11:54 AM, David Grant <[email protected]> wrote: >> >> I don't waste my time with playground anymore. It requires a lot of >> processing power and doesn't provide enough benefit for the frustration it >> leads to. >> >> Sent from my iPad >> >>> On Jun 26, 2015, at 9:19 AM, Fritz Anderson <[email protected]> wrote: >>> >>> The playground crashes repeatedly, drops alerts, and jumps the insertion >>> point (with loss of typed characters) to the top of the file. This will (I >>> hope) be corrected in the beta that according to patten should be out week >>> after next, but in the mean time it’s frustrating to read all the blogs on >>> what people are delighted to find in Swift 2.0. >>> >>> I hope someone has a workaround or a direction I can pursue. >>> >>> I’ve already posted a forum question >>> (https://forums.developer.apple.com/message/15886) and submitted a Radar >>> (rdar:///21555545)… >>> >>> Xcode 7.0b2, OS X 10.10.3 or 10.11b2; OS X playground, 10.11 SDK. >>> >>> >>> ## Exception >>> >>> It throws an exception, logged in Console.app as: >>> >>> ---- >>> Unable to create target for stub executable. >>> unable to find executable for >>> '/var/folders/2n/k51s3_gd2177vkrmy04p2s000000gn/T/com.apple.dt.Xcode.pg/applications/modeling-54310-7.app/Contents/MacOS/modeling' >>> ---- >>> >>> /var/folders… usually contains an .app with a serial number one higher; >>> 54310-8 in this case. >>> >>> >>> ## Things that have no effect >>> >>> Closing and reopening the project, with or without quitting Xcode or >>> rebooting in between. >>> Closing the project and deleting the derived-products folder (or the >>> project itself) from the Projects organizer. >>> Single or multiple pages. (I first saw this after I added a page, but if it >>> persists after all these permutations, surely it’s a red herring.) >>> Deleting the directory in /var/folders, even as high as the child of >>> /var/folders (it is restored, apparently in full, immediately). >>> Deleting ~/Library/Developer/ and ~/Library/Preferences/com.apple.dt*, >>> logging out then in. >>> Copying source into a new project, then adding a playground. >>> Same results on 10.10.3 and 10.11b2 >>> >>> On and on, usual caveat that it’s impossible to ring the changes on _all_ >>> the permutations. I guess I should try a reboot with the Shift key. I don’t >>> knowingly install hacky .kexts (iStat Menus?), but if everything’s correct, >>> then the bug doesn’t exist, right? >>> >>> ## Plea >>> >>> Any suggestions on how I can get a working playground? >>> >>> — F > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Xcode-users mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/xcode-users/dmgrant%40infinitydigital.com > > This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
