It's absurd to have to beg the wealthiest software company in the world for what should be considered really basic stuff. Xcode is consistently unstable, slow, missing simple essential functionality (like refactoring), and Apple's interface builder is something that most experienced Apple devs know to run for the hills from.
I remember a few years ago, at a WWDC session on Xcode, the presenter was talking about version control improvements. He said something to the extent of "Xcode has a robust version control system" and the crowd laughed. And the presenter got offended, said it "wasn't nice" of the audience to laugh considering how hard-working the Xcode team was. My recollection is blurry so it would be nice if someone else remembers…
Dear Apple
61–70 of 211 posts
Re: Dear Apple
#62Wow, it's that bad for developers of their own platform? I do rails development and left OSX for linux a few years ago after finding all the custom song & dance to do things on apple was painful. Not a day goes by I am not grateful for doing that, i am much happier doing web dev on a linux box. But I was under the impression Apple at least took care of the devs who work on their platforms. As someone else has noted:…
Can you give some examples of advantages of doing ROR development on Linux vs Mac?
my dev machine is a VM, which gives me a ton of other benefits, like portability, resizability, backups, versioning, and overall stability. I can (and have) given devs my VM to get up and running immediately on a complex project, without having to do a lot of setup.
With each OSX update, usually stuff broke, needed to be reinstalled, or performed differently. With Linux, that is not the case. And with a linux VM, I can ride out host upgrades and keep plugging away with a machine i know works - or attempt an upgrade on a cloned VM and have a trivial way to backtrack if it fails.
Re: Dear Apple
#63It's absurd to have to beg the wealthiest software company in the world for what should be considered really basic stuff. Xcode is consistently unstable, slow, missing simple essential functionality (like refactoring), and Apple's interface builder is something that most experienced Apple devs know to run for the hills from.
The one that's been getting me lately is the split between Xcode 7/Swift 2.2 and 8/3. We have an older project in Swift 2 (yes, it's slated to get changed over, just not yet), and new work on a project in 3. If I try to open one while the other is already open, one of the Xcodes invariably freezes or crashes. I will say, though, that I've always liked IB (though not storyboards). But then there's the wonderful "Oh, y…
Re: Dear Apple
#64Wow, it's that bad for developers of their own platform? I do rails development and left OSX for linux a few years ago after finding all the custom song & dance to do things on apple was painful. Not a day goes by I am not grateful for doing that, i am much happier doing web dev on a linux box. But I was under the impression Apple at least took care of the devs who work on their platforms. As someone else has noted:…
Can you give some examples of advantages of doing ROR development on Linux vs Mac?
Re: Dear Apple
#65Just stop pushing apps for iProducts. When all the major apps stop adding features for a while Apple will focus on getting developers back or customers switch to Android.
Re: Dear Apple
#66Earlier quoted context omitted.
Yup, that. Vote with your keyboards. Apple writes software with the same tools and languages - if they considered this stuff a problem, they'd have fixed it by now. Besides, Apple has mechanisms for feedback, and it's not open letters on GitHub.
> if they considered this stuff a problem, they'd have fixed it by now It's not good but it's workable. Which Apple accepts as a reason to focus very few resources on dev tools.
Re: Dear Apple
#67It's absurd to have to beg the wealthiest software company in the world for what should be considered really basic stuff. Xcode is consistently unstable, slow, missing simple essential functionality (like refactoring), and Apple's interface builder is something that most experienced Apple devs know to run for the hills from.
Sooner or later people will wake up to the fact that this is their own fault for leveraging a proprietary ecosystem. You want to play in Apple's walled garden, you take the scraps they give you. They have no financial incentive to make the experience better for you if you're already a captive developer.
And one of the reason the bigger spending customers are with Apple is the benefits of the walled garden. It's more secure, and it's updated far faster (or at all). For developers it's a better environment to develop for, consistent screen sizes and hardware features and I know I can write my latest app for the latest iOS and within months of it's release the vast majority of revenue producing customers will be on it. That's a big reason why better apps are written on iOS first, it's easier.
Re: Dear Apple
#68Earlier quoted context omitted.
It's only unrealistic if you aren't willing to adapt to changing market conditions.
This may not be what HN readers want to hear, but users, not developers, have the primary influence over what the market is.
Re: Dear Apple
#69Just stop pushing apps for iProducts. When all the major apps stop adding features for a while Apple will focus on getting developers back or customers switch to Android.
Unpopular advice here in HN but I honestly advice people to think twice about devoting all their career to technologies made and developed for a single company, there are some big risks there, you never know what Apple will do in the future.
Re: Dear Apple
#70These letters always come off as sounding immature. The open letter, the why I quit, the why I switch letters all do. It is as if you need validation for something.