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

131–140 of 179 posts

Re: What's new in Xcode 7

#131

Post by chc »

biturd wrote: post #103
chc wrote: post #60

Earlier quoted context omitted.

> Honestly, if you're charging users, then there's absolutely no question about it, you get the membership. Your entire "expecting the user to do so" point completely goes out the window the second you said it's a paid app. If you have the revenue, then it's simply a cost of doing business in the Apple world. Yes, because Apple demands rent. They create a problem and then charge you to fix it. This is called rent-see…

Do you have a link to the patio11 anecdote?

I'm having trouble finding the anecdote itself where the customer was angry about the change in Googles. Maybe it was in a podcast rather than on HN -- hard to remember, it was several years ago. Here's a later post where he was discussing what he'd learned from incidents like that: https://news.ycombinator.com/item?id=1808001

Re: What's new in Xcode 7

#132

Post by e28eta »

cellularmitosis wrote: post #121
smtddr wrote: post #87

Earlier quoted context omitted.

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

"The standard Cocoa convention is that exceptions signal programmer error and are not intended to be recovered from. Making code exceptions-safe by default would impose severe runtime and code size penalties on code that typically does not actually care about exceptions safety. Therefore, ARC-generated code leaks by default on exceptions, which is just fine if the process is going to be immediately terminated anyway. Programs which do care about recovering from exceptions should enable the option."

http://clang.llvm.org/docs/AutomaticReferenceCounting.html#e...

Re: What's new in Xcode 7

#133

Post by chc »

biturd wrote: post #104
chc wrote: post #60

Earlier quoted context omitted.

> Honestly, if you're charging users, then there's absolutely no question about it, you get the membership. Your entire "expecting the user to do so" point completely goes out the window the second you said it's a paid app. If you have the revenue, then it's simply a cost of doing business in the Apple world. Yes, because Apple demands rent. They create a problem and then charge you to fix it. This is called rent-see…

I feel being a staunch Mac user from the beginning has been detrimental to me. My first computer was a commodore 64, which I typed the programs out of the book into the terminal and it made balls move around on the screen and such. But I was really young, and no one was there to catch me, so I never thought to fiddle with it, I thought it was like a set of instructions and you had to follow them. I did not yet unders…

Well, I was talking about OS X, which was released around 2000, probably much later than your Mac Plus days. OS X included a whole Unixy environment and shipped the Developer Tools (GCC + the precursor to Xcode) on a second CD. I had already done some programming before that, though, in Mac game-making software (World Builder and Adventure Simulator), and with JavaScript on the Web, but the ability to really program my computer with Objective-C and Cocoa was amazing.

There was also a free development environment by Apple for OS 8 (maybe earlier, I don't know) called MPW. I think it was originally a paid product, but Apple ended up just giving MPW away because everybody used CodeWarrior. But I found it difficult to use and didn't get much further than some basic C lessons I found somewhere on the Internet. All the more advanced stuff I found wouldn't work (I think it was probably targeted at Windows or Unix, but all I knew at the time was that MPW couldn't compile it).

Re: What's new in Xcode 7

#134

Post by pjmlp »

0x0 wrote: post #43
Entalpi wrote: post #34

"Xcode 7 has a ENABLE_BITCODE option to embed bitcode in apps, app extensions, and frameworks. The option is turned on by default for iOS and is mandatory for watchOS projects submitted to the store. When bitcode is enabled for a target, all the objects, static libraries and user frameworks used when linking that target must contain bitcode. Otherwise, an error or a warning will be issued by the linker. (Note: missin…

Wow, that's quite a change! Is this some kind of intermediate LLVM language? Sounds very Java/.NET-like. I can see how it's nice for future proofing (i bet you can even change from ARM to x86 then!), but you're handing a lot of control and probably something much closer to the original source code over to Apple. Is there a fundamental change of architecture planned for future iOS devices?

Apple is just following Microsoft footsteps.

http://channel9.msdn.com/Shows/Going+Deep/Mani-Ramaswamy-and...

https://msdn.microsoft.com/en-us/library/dn584397%28v=vs.110...

Re: What's new in Xcode 7

#135

Post by coldtea »

beagle3 wrote: post #115
gruez wrote: post #88

Earlier quoted context omitted.

>thanks to Developer ID, they at least had some kind of payment trail as well as a name, likely making it harder for the same person to get additional certificates What's preventing me from paying some person in a third world country to get a certificate in his name?

Nothing does. But that person will likely have no loyalty to you, and would give every info he has about you to Apple for an additional $100. You don't need to be NSA level to hide your tracks there, but it's not trivial either. And Apple is likely to work with the FBI/Interpol about that if whatever evil deeds your software does is sufficiently high profile. Theses guys might also not be good enough to catch you - b…

Plus that certificate will be revoked pronto.

Re: What's new in Xcode 7

#136

Post by coldtea »

rattray wrote: post #100
hueving wrote: post #77

Earlier quoted context omitted.

I think devs that can dump money on apple products but not on the $99/year are a pretty slim slice of the population.

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.

Re: What's new in Xcode 7

#137

Post by arihant »

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 make you buy a new Mac per developer every 2 years.

Re: What's new in Xcode 7

#138

Post by coldtea »

hrabago wrote: post #126
MCRed wrote: post #112

Earlier quoted context omitted.

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

40% of mobile developers don't have good apps. Heck, more like 90% of them don't (Sturgeon's law).

Re: What's new in Xcode 7

#139

Post by coldtea »

0x0 wrote: post #53
Someone wrote: post #49

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

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?

Re: What's new in Xcode 7

#140

Post by coldtea »

mp_mn wrote: post #95
overgard wrote: post #82

Earlier quoted context omitted.

I feel like a lot of basic stuff is broken or non-existent in Xcode. For instance, project text search on my machine freezes up the entire IDE for half an hour, which is ridiculous since A) it's not an unusually large project, and B) it's on an SSD, and it should be running search in a separate thread anyway.. Not to mention last time I used Xcode (6.2) it crashed on me 7 times in the span of an hour on basic things,…

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.
Post reply on HN