I wonder if it's possible to do ad-hoc testing on Xcode 7 without joining the developer program?
What's new in Xcode 7
161–170 of 179 posts
Re: What's new in Xcode 7
#162Earlier quoted context omitted.
This is the first time you could install apps on your device without paying for a membership. Previously you could design and test through a simulator for free, now he can build and actually use his app without paying extra as he isn't distributing.
You can always distribute, but you can't submit to the mac app store. I used to run a multitude of OSX (xcode developed) applications for beta testing, and while not signed, they were indeed runable.
I think you two are talking about different things. You could always distribute to OSX devices. However, now is the first time ever when you can run your app on an iOS device without a membership certificate from Apple. This is very good news.
Re: What's new in Xcode 7
#163Earlier quoted context omitted.
Where do you live?
Did you read what he said? It doesn't matter when on the world he lives because his argument is based on a ratio, and that's invariant. That people that can drop money on Apple hardware but can't afford $100 per year doesn't make sense, for the obvious reason that Apple hardware costs many times that.
Back when I was at school I developed some iOS apps, and the $100 was huge where I lived. That's literally 1/4 of minimum salary there. I worked the entire summer holiday to afford an old mac mini(which was really crap,but that was the minimum spec which could run Xcode), and then actually had to borrow money to pay the $100 fee. That's why I prefered android from the start - it was just easier to start developing, with much smaller fee and no membership required to actually deploy to Android devices.
Re: What's new in Xcode 7
#164Earlier quoted context omitted.
http://llvm.org/docs/BitCodeFormat.html . Way closer to assembly than Java/.NET byte codes. Also potentially processor specific. My guess is that it is future-proofing towards running iOS apps on Mac OS and/or running (parts of) iOS apps on the Apple Watch. It also might mean that Apple plans to make their own ARM extensions (for example, I suspect having the CPU know about tagged pointers, so that an 'add' instructi…
> also allows your app to download some resources on demand. Oh boy; if this is the start of apps lazy-loading resources and code, I'm really excited. It's the largest barrier to signing in your account from any device.
There's new higher level stuff for downloading assets on the fly from the App Store, check out the new NSBundleResourceRequest class.
Re: What's new in Xcode 7
#165Earlier quoted context omitted.
I have to ask, because I feel XCode is the worst IDE I've ever used. What about it is pretty awesome? Instruments is pretty cool, though.
There's no way Xcode is the worst you've ever used unless your opinion is just based on personal preference (which is fair enough but not really relevant to the rest of us) I don't think I'd say it's better than VS if that's all you're comparing it to, but it's pretty much on par. When I last used VS heavily it seemed marginally more robust than Xcode but the only real feature I liked vs. Xcode was the ability to use…
The other IDE's I've worked with for any significant amount of time are Eclipse, Visual Studio, and various flavors of IntelliJ. Eclipse is the worse of the bunch, but it has a few important features that XCode doesn't. Support for a multi-monitor setup, configuration files that don't cause conflicts every other merge, a complete set of refactoring options. That XCode doesn't have a Search Usages or equivalent for a symbol, forcing you to use text search, is downright weird; they clearly use that functionality internally in the Rename refactoring.
Stability wise, there have been a few versions that crashed a lot, but that has improved lately, so I'm not complaining. And I do love how quickly it opens.
I'm currently using AppCode for developing for iOS, and I find substantially better than XCode. It has a full set of refactoring tools, that I use constantly, better search, it actually creates folders when you create groups (unless you tell it not to, and I think that's the sane default). I'm not sure it's a fair comparison, since it does cost as a much as a Developer License.
Re: What's new in Xcode 7
#166Earlier quoted context omitted.
I have to ask, because I feel XCode is the worst IDE I've ever used. What about it is pretty awesome? Instruments is pretty cool, though.
Everything. The way debugging is integrated. Interface Builder-- nobody has anything like that to compete with it. It's totally integrated so you can really develop efficiently, and the simulator makes testing quick and easy. I've never seen an IDE that was anywhere close. I suspect that people who hate Xcode are simply familiar with something else and find it frustrating to use it (though they've spent a few hours w…
I've used XCode for hundreds of hours. It's very lacking in functionality, I'm not going to copy and paste my other comment.
Interface Builder is very nice, I will give it that. I did have it break on me once or twice(wouldn't let met add a particular kind of segue), and having to manually edit the generated XML file was a pain, but still, it is better than most similar things I've used.
Re: What's new in Xcode 7
#167Every year the new XCode comes, and I'm less excited about new features and more worried about how many more Macs will I have to buy. Last update on XCode 6 made it impossible for some 2012 models to run it. This update is almost surely for Yosemite and above. The cost of developing on Apple platform is crazy these days. I miss the days when they could mock Microsoft for having an expensive Visual Studio. Now they ma…
"Last update on XCode 6 made it impossible for some 2012 models to run it" I find this difficult to believe, care to provide evidence of it being an Apple problem?
Macbook Air 2012 models with 4GB soldered RAM ran fine on Mavericks and XCode 6, until Apple decided the newest XCode 6 to be Yosemite only. Now Yosemite is free, but is absolute abonimation on 2/4GB machines. On top of that, you have to run XCode. Not to mention the time debt required to upgrade.
Now, for indie developer setting, these issues might not be huge. But the problem here is - Apple puts businesses in awkward positions, when they have to bulk buy RAMs and upgrade all the systems just to compile on the newest minor release of iOS. Then, they started soldering RAM, so now to compile on 8.3, buy 25 new Macs or fuck off.
Apple's actions that screws us - solder RAM, make only latest XCode work with latest SDK, make OS impossible to run on low RAM, make XCode run only on newest OS.
Re: What's new in Xcode 7
#168Earlier quoted context omitted.
They just added generics to Obj-C, which is one of the biggest new language features in a long time.
I guess that is just required for interoperability with Swift. Generics don't make much sense in Objective-C dynamic model.
Funny you should mention that. Quoting Apple's own docs:
> Objective-C lightweight generics are ignored by Swift. Any other types using lightweight generics are imported into Swift as if they were unparameterized.[1]
So it doesn't look like the goal here is Swift interop.
[1]: Excerpt from Using Swift with Cocoa and Objective-C (Swift 2 Prerelease) https://itunes.apple.com/us/book/using-swift-cocoa-objective...
Re: What's new in Xcode 7
#169Earlier quoted context omitted.
No, you only need to pay if you want to distribute apps through the App Store.
Is that right? As of Mavericks, OS X by default refuses to run applications that are not signed with a 99$/year Apple certificate.
certificate signing is free. always has been. it's the app store part that costs you.
Re: What's new in Xcode 7
#170Earlier quoted context omitted.
"Last update on XCode 6 made it impossible for some 2012 models to run it" I find this difficult to believe, care to provide evidence of it being an Apple problem?
Macbook Air 2012 models with 4GB soldered RAM ran fine on Mavericks and XCode 6, until Apple decided the newest XCode 6 to be Yosemite only. Now Yosemite is free, but is absolute abonimation on 2/4GB machines. On top of that, you have to run XCode. Not to mention the time debt required to upgrade. Now, for indie developer setting, these issues might not be huge. But the problem here is - Apple puts businesses in awkw…
Well that is just stupid, the macbook air is not a dev machine. Get a macbook pro or an imac and you are fine. Apple did not screw you, you screwed yourself for buying the cheapest they had to offer.