Live data from Hacker News

What's new in Xcode 7

developer.apple.com

101–110 of 179 posts

Re: What's new in Xcode 7

#101

Earlier quoted context omitted.

This was the big news IMO. Many would-be developers reside in countries where $99/year is a huge amount of money that cannot be justified until they have a final, working product they are ready to distribute.

Yet those developers somehow can buy a computer for $1000+ and spend an additional $500-$800 on the tablet/phone? :)

In cash? Ok

With credit card? not!

And in my case, is necessary to fax(!) apple and do banking stuff that is a problem if you have credit problems

Re: What's new in Xcode 7

#102

Earlier quoted context omitted.

This was the big news IMO. Many would-be developers reside in countries where $99/year is a huge amount of money that cannot be justified until they have a final, working product they are ready to distribute.

Yet those developers somehow can buy a computer for $1000+ and spend an additional $500-$800 on the tablet/phone? :)

Not everyone making iOS apps has Apple hardware. I was just at a React Native meetup in Bangalore where half the audience was on Dells running Ubuntu, trying to install hackintosh VM's so they could use XCode and the emulator.

The passion for building things doesn't only strike those with four figures of disposable income, you know :)

Re: What's new in Xcode 7

#103
post #60

Earlier quoted context omitted.

> I don't feel comfortable charging people for something they might not even be able to run. 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. Plus, once again,…

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

Re: What's new in Xcode 7

#104
post #60

Earlier quoted context omitted.

> I don't feel comfortable charging people for something they might not even be able to run. 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. Plus, once again,…

> 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 understand creativity at that age.

I then later, many years later, was given a Mac Plus. I could use BBS software to chat, but remember thinking, it is very hard to even type a conversation back and forth to a user elsewhere with a modem. There really was no software for it, or if there was, it was hard to find or even know about.

How did you know to learn C and then get a compiler? And how did you afford the software to develop back then? Wasn't code warrior around several thousand?

Re: What's new in Xcode 7

#105
post #62
post #40

Earlier quoted context omitted.

I could afford $100 a month. Affordability is not the point. The point is that Apple will block your app from opening by default unless you pay them a recurring fee, and if not, you must incur additional support burden to teach users how to get around the problem. Yes, lots of apps do post instructions on how to get around it, but lots of apps do all sorts of user-unfriendly things. We Apple users used to make fun of…

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.

Re: What's new in Xcode 7

#106
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."

Not being a developer for Apple products, what has changed?

You used to have to get a $99 developer membership to put apps on your iPhone.

Re: What's new in Xcode 7

#108
post #65
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?

Wait, you can't auto-rename stuff? I noticed in an older version of XCode (when I still bothered), that there were really basic refactoring tools missing for C++, but I assumed that was just because Apple hates C++. Apple obviously doesn't hate Swift. I guess Apple just hates refactoring. Why though?

> but I assumed that was just because Apple hates C++

Chris Lattner is a bit of a C++ head, no? LLVM is a C++ project...

With that said, yea, refactoring support in Xcode is a drag.

Re: What's new in Xcode 7

#109
post #65
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?

Wait, you can't auto-rename stuff? I noticed in an older version of XCode (when I still bothered), that there were really basic refactoring tools missing for C++, but I assumed that was just because Apple hates C++. Apple obviously doesn't hate Swift. I guess Apple just hates refactoring. Why though?

I remember having access to Refactoring in an old Objective-C project, but it was far from "refactoring" - it would have been better named "find-and-replace", considering it substituted some occurrences of the word in question in comments, strings, etc, often with incorrect casing.

Re: What's new in Xcode 7

#110
post #87
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…

While Swift was designed to interface well with Objective-C and runs on the Objective-C runtime, it is not a wrapper around Objective-C. It was written from the ground up, started by Chris Lattner at Apple.
Post reply on HN