Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

What's new in Xcode 7

developer.apple.com

Post reply on HN
Print view View original

121–130 of 179 posts

Re: What's new in Xcode 7

#121

Post by cellularmitosis »

smtddr wrote: post #87
halayli wrote: post #15

"Advanced error handling model using try / catch / throw that feels natural in Swift." yeah try/catch is very advanced.

You have to understand though, Swift is like a really nice wrapper around Objective-C. Imagine adding try/catch to C programming language? I know python & java and all of today's relevant high-level languages have it since forever, but implementing that in something that wasn't designed for it from the start is a big task. I'm by no stretch of the imagination an Apple fanatic but as a person who is about to send out…

Obj-C already had try / catch, it just wasn't considered idiomatic to the platform. Amazon caught a bunch of flak when they wrote an Obj-C interface to AWS and all of the error handling was try/catch instead of NSError (probably, they just line-for-line transliterated their Java interface).

Re: What's new in Xcode 7

#122

Post by cellularmitosis »

msie wrote: post #107

Stack Views is really cool! I don't need the full power and complexity of AutoLayout.

I saw them as being more of a replacement for UITableView for the cases where you don't need all of its dynamism (cell re-use, etc), and whipping together half a dozen static table cells involves too much ceremony. In fact I was hoping I'd be able to use Stack Views to get in the ballpark and then do final tweaking with AutoLayout...

Re: What's new in Xcode 7

#123

Post by cellularmitosis »

zimbatm wrote: post #36

> A migrator in Xcode 7 to convert your existing your existing Swift code to use the new Swift 2.0 features and syntax. woops, repetition !

Chris seemed to indicate that this migrator will also somehow handle the migration from NSError-style error handling to the new try/catch. I'm very curious to see how sophisticated that will be.

Re: What's new in Xcode 7

#124

Post by donarb »

slm_HN wrote: post #99
Thiz wrote: post #98

Can I use it on my old mac mini 2011 with 2gb ram and Mavericks? I really want to start using Swift. And no, can't upgrade.

I doubt it. The last version of XCode 6 won't run without Yosemite, so I'm guessing 7 will require Yosemite. Also it's very hard to run with 2gb ram. For example you won't be able to use the iOS emulator because the swapping will take so long XCode will timeout when trying to launch the emulator. It's very painful even with 4gb. 8 is probably the minimum.

It's a simulator, not an emulator. There's a big difference.

Re: What's new in Xcode 7

#125

Post by mcintyre1994 »

glhaynes wrote: post #2

Unexpected: "Xcode 7 and Swift now make it easier for everyone to build apps and run them directly on their Apple devices. Simply sign in with your Apple ID, and turn your idea into an app that you can touch on your iPad, iPhone, or Apple Watch. Download Xcode 7 beta and try it yourself today. Program membership is not required."

Is this a path to non jailbreak sideloading at least for users with OSX and Xcode7? Not exactly likely to make a splash but interesting move if you can share these projects without too much fuss.

More generally, this is an awesome move. Kudos to Apple :)

Re: What's new in Xcode 7

#126

Post by hrabago »

MCRed wrote: post #112
sangnoir wrote: post #97

Earlier quoted context omitted.

> Yet those developers somehow can buy a computer for $1000+ and spend an additional $500-$800 on the tablet/phone? :)[1] In a word - Yes. I am a developer from a 3rd world country, and I bought a Mac Mini for $500 (not '$1000+') for the purposes of entering the Apple ecosystem. I'm not going to spend another $500 on an iPhone[2], especially since I'm not sure if it will work out financially. The emulator will have t…

If you're serious about making an App, then yes, you should spend the $100. You will get it back in the first couple of days if you make a good app. The $100 is to keep out the shovel ware and crap-- look at all the junk in the store as it is now. Imagine what it would be like if there wasn't that $100 barrier to entry?

> you should spend the $100. You will get it back in the first couple of days if you make a good app.

40% of mobile developers do not even reach $100 in a month [1]. Having a "good app" is not a guarantee that someone will get $100 in two days.

[1] https://www.developereconomics.com/reports/developer-economi...

Re: What's new in Xcode 7

#127

Post by s73v3r »

lultimouomo wrote: post #17
donarb wrote: post #7

Earlier 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.

That's complete and utter horse shit.

Re: What's new in Xcode 7

#128

Post by m4x »

Fargren wrote: post #105
m4x wrote: post #62

Earlier quoted context omitted.

Apple isn't forcing you to pay if you want to run your apps, they're warning users and forcing them to take an extra step to run unsigned code. That doesn't completely prevent malicious code execution but it definitely helps which is a net win for users. Complaining that they ask for $100/year to use their official distribution channel (which incurs ongoing costs for them) seems unreasonable considering the quality a…

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 C# rather than Obj-C (which is less relevant now that Swift exists)

Other than that, every single IDE I can think of is relatively unpolished and if you're developing specifically for OS X then the alternatives are practically useless.

I'm really glad Xcode finally has automated GUI testing

Re: What's new in Xcode 7

#129

Post by [deleted] »

Fargren wrote: post #105
m4x wrote: post #62

Earlier quoted context omitted.

Apple isn't forcing you to pay if you want to run your apps, they're warning users and forcing them to take an extra step to run unsigned code. That doesn't completely prevent malicious code execution but it definitely helps which is a net win for users. Complaining that they ask for $100/year to use their official distribution channel (which incurs ongoing costs for them) seems unreasonable considering the quality a…

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.

[deleted]

Re: What's new in Xcode 7

#130

Post by s73v3r »

giarc wrote: post #86
laydownlarry wrote: post #57

Earlier quoted context omitted.

you misspelled cheap

Sure, cheap/thrifty whatever. However, I'd rather pay for the dev account when I actually need it. I don't see a huge benefit to paying $100/year while in development. I can accomplish everything I want without it. Once I'm ready to publish the app in the app store, I'll gladly pay $100/year.

And you don't consider showing clients to be "needing it"? If I were a client, I'd be questioning how serious you were.
Post reply on HN