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

151–160 of 179 posts

Re: What's new in Xcode 7

#151

Post by 72deluxe »

Someone wrote: post #45
Joky wrote: post #37

Earlier quoted context omitted.

Advanced != Exclusive/Innovative/... That said, the spec here is a bit different than C++ exception I believe.

Agreed. Also, it does look different aka innovative to me: func loadData() throws { } func test() { do { try loadData() } catch { print(error) } } I guess that you have to prefix any statement that might throw with 'try', and cannot prefix other statements with it. If so, their motto really seems to be 'explicit over implicit'. I'm not sure that is an improvement, but I'm not sure that it is bad, either, provided t…

Doesn't that mean typing try a million times instead of putting potentially throwable calls inside one try block and a bunch of different catch handlers?

I wonder why they insist on that. Perhaps it is easier to parse?

Re: What's new in Xcode 7

#152

Post by 72deluxe »

arihant wrote: post #137

Every 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…

2012 Macs couldn't run xcode?

I'm running a 2008 Mac Pro running Xcode 6 and Yosemite. I have a 2012 MacBook Pro at home running Yosemite and Xcode 6 (but my word is the hard disk in that slow - luck of the draw getting a 5200 Hitachi or a Samsung, eh!!!)

Which 2012 Macs can't run Xcode 6?

Re: What's new in Xcode 7

#153

Post by 72deluxe »

beagle3 wrote: post #117
nekitamo wrote: post #54

Earlier quoted context omitted.

Agreed, this is an insane requirement. Our app uses commercial libraries from closed source vendors, some of which are no longer distributing newer versions of their libraries. If this becomes a requirement, we will not be able to ship our app because we can't deliver the entire thing in bitcode.

> Our app uses commercial libraries from closed source vendors, some of which are no longer distributing newer versions of their libraries This is the insane part - you're relying on things you have zero control over and zero support for. Apple's requirement is no different than some fatal bug discovered or backdoor discovered in those libraries - except Apple is giving you some notice without immediately putting the…

I would agree. They're relying on things they don't have control over. That's bad.

Re: What's new in Xcode 7

#154

Post by 72deluxe »

coldtea wrote: post #140
mp_mn wrote: post #95

Earlier quoted context omitted.

Is your search scope too broad? Too many Pods maybe? I've never had an issue with project text search. The only time I've ever had that many problems in an iOS dev workflow was years ago when I was briefly running OSX through VMWare. There's something else going on with your environment, it shouldn't be giving you this many problems.

He probably (obviously?) has some corrupted Spotlight index.

Does xcode use Spotlight for search? I don't think it does. It clearly pounds the disk when searching but as Spotlight is optional and you can choose to not index various locations, relying on Spotlight for search (and being unable to search locations x, y and z) would mean that xcode would not find results in x, y, and z.

Re: What's new in Xcode 7

#155

Post by 72deluxe »

Fargren wrote: post #58

Not even a mention of refactoring tools for Swift? Right now you can't even do a Rename. This was one of the biggest reasons I bought Appcode, actually. And I'm still waiting for either IDE to implement Extract Method. It boggles my mind how little I hear people complain about this. Aren't these basic tools by now?

I wonder if they'll implement refactoring tools for C++ first. Really old language, zero support for refactoring in xcode....

Re: What's new in Xcode 7

#156

Post by 72deluxe »

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.

Ouch. 2GB RAM? Sleeping and resuming must be really fast (no large capacity of RAM to save to disk) but daily running must be painful.

Re: What's new in Xcode 7

#157

Post by equoid »

arihant wrote: post #137

Every 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?

Re: What's new in Xcode 7

#158

Post by [deleted] »

chc wrote: post #32
ceejayoz wrote: post #21

Earlier quoted context omitted.

You can always right-click and select "Open".

I can do that, but it's not reasonable to expect my users to do so. As it is, indie developers have to choose between paying rent to Apple and having most users unable to open their apps.

[deleted]

Re: What's new in Xcode 7

#159

Post by SwellJoe »

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?

When I recently worked on making our installer work on Mac OS X again (it broke a few years ago, and we don't have a lot of demand for Mac OS X, since we build server software), I did so in a VM on my Linux system. It was slow, it was ornery to get it working, but it was free (if we assume a pirated Mac OS X, though I have a purchased box of a slightly older version than the one I was able to install from a prior Hackintosh experiment that I gave up on, since I found I hate Mac OS X through and through).

I would never build for Mac or iOS if I had to buy a Mac. Since I was able to do so effectively for free, Mac support in our software (which is pretty popular with about 3+ million downloads a year) got a lot better. I didn't enjoy it, and I won't be using that VM for anything other than testing Mac OS X support, but it's silly to act like everyone ought to be willing to shell out money to support a platform (especially in our case, where the vast majority of our paying users are running Linux).

"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?"

Whatever happened to the argument that the Apple approval process was to protect users from poor quality software?

Re: What's new in Xcode 7

#160

Post by 0x0 »

coldtea wrote: post #139
0x0 wrote: post #53

Earlier quoted context omitted.

Oh ok. So would you need two sets of bitcodes to target ios32 and ios64? A lot of fundamental types like CGFloat have different sizes...

Would iOS32 be supported at all?

They say iOS9 will support iPhone4s so it must be?
Post reply on HN