Live data from Hacker News

Xcode Constantly Phones Home

lapcatsoftware.com

51–60 of 63 posts

Re: Xcode Constantly Phones Home

#51

Makes sense, and it is annoying, but there’s a lot of annoying stuff in Xcode. Looking at the console can get rather depressing. There’s a lot of “noise” in there, that is basically sound and fury, signifying nothing. I get tired of googling errors and warnings (I compile -wall, and take every warning seriously), only to realize they are meaningless “background noise,” due to the system trying to generate code for pl…

I mean you're going to tell me that this a rehash of what the Stack Overflow people told you but the reason this is a warning is because the external name is meant to aid in readability but the internal name is the one that is actually operated on, so the latter is the one that is actually relevant when documenting what the thing actually is. It would be unreasonable to write documentation for a parameter called "in"…

[deleted]

Re: Xcode Constantly Phones Home

#52

Although the title was not changed, if you don't read the actual post, it's misleading. It makes connections to Apple when you launch it, and when you open project files. It also makes connections when you build, although that is to be expected, since signing is required for uploading builds to the store. It does not "constantly" phone home.

>It does not "constantly" phone home.

Just whenever you do anything major. I'd call that constantly.

Re: Xcode Constantly Phones Home

#53

Makes sense, and it is annoying, but there’s a lot of annoying stuff in Xcode. Looking at the console can get rather depressing. There’s a lot of “noise” in there, that is basically sound and fury, signifying nothing. I get tired of googling errors and warnings (I compile -wall, and take every warning seriously), only to realize they are meaningless “background noise,” due to the system trying to generate code for pl…

> Looking at the console can get rather depressing Opening Console and watching critical error messages stream in at an alarming rate when you do basically anything in the entire OS, is a great way to remind yourself just how bad Apple’s software quality has gotten. They're absolutely drowning in bugs. I just opened it, after waking my laptop up from sleep, and about 10,000 errors+warnings have streamed in in the pas…

but it is all a success! (customers are paying money for products) /s

Re: Xcode Constantly Phones Home

#54

Makes sense, and it is annoying, but there’s a lot of annoying stuff in Xcode. Looking at the console can get rather depressing. There’s a lot of “noise” in there, that is basically sound and fury, signifying nothing. I get tired of googling errors and warnings (I compile -wall, and take every warning seriously), only to realize they are meaningless “background noise,” due to the system trying to generate code for pl…

The example warning is the Swift language warning about style conventions, there's an interesting conversation about whether enforcing style conventions through warnings is appropriate, but that's is a Swift language question, not an Xcode question.

Re: Xcode Constantly Phones Home

#55

Although the title was not changed, if you don't read the actual post, it's misleading. It makes connections to Apple when you launch it, and when you open project files. It also makes connections when you build, although that is to be expected, since signing is required for uploading builds to the store. It does not "constantly" phone home.

Yes and no. "Constantly" in the title means "with regular occurrence", like, I'm constantly being a pain in the neck with my word explanations. And the "constantly" you mean is more like "continuously". And you are both right, it's just that language in imprecise.

https://www.merriam-webster.com/dictionary/constantly

Re: Xcode Constantly Phones Home

#58

Everything Apple constantly phones home. (It wasn't always this way.) Will the blog author switch away from using Apple computers and writing software for them. No doubt he has some convincing list of excuses.

> Will the blog author switch away from using Apple computers and writing software for them. No doubt he has some convincing list of excuses.

No doubt. Here's my list:

1. That's how I make a living.

Now I urge you to consult this list, the HN Guidelines: https://news.ycombinator.com/newsguidelines.html

Re: Xcode Constantly Phones Home

#59

Makes sense, and it is annoying, but there’s a lot of annoying stuff in Xcode. Looking at the console can get rather depressing. There’s a lot of “noise” in there, that is basically sound and fury, signifying nothing. I get tired of googling errors and warnings (I compile -wall, and take every warning seriously), only to realize they are meaningless “background noise,” due to the system trying to generate code for pl…

> Looking at the console can get rather depressing Opening Console and watching critical error messages stream in at an alarming rate when you do basically anything in the entire OS, is a great way to remind yourself just how bad Apple’s software quality has gotten. They're absolutely drowning in bugs. I just opened it, after waking my laptop up from sleep, and about 10,000 errors+warnings have streamed in in the pas…

I hate to be pessimistic but I have to agree. I have filed a number of bug reports, about Logic Pro for example. I try to be detailed and a number of them should have been real gimmes, but it seems that half the time somebody just asks for a crash dump or example file to ignore it.

Re: Xcode Constantly Phones Home

#60
post #2

Privacy is only for app users, not app developers

And with Apple, even as a user, privacy mostly means a "what happens in Vegas stays in Vegas" type of deal.

Well, they did advertise in such a manner at one point.

https://9to5mac.com/2019/01/05/apple-privacy-billboard-vegas...

Post reply on HN