Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
As a developer, this is not good when I'm trying to develop for iOS8-only features. People need to move away from iOS 7 quicker.

The combination of bugs in iOS 8, and the fact that it required WAY too much space, really is slowing adoption.

I hope with iOS 9 we'll see it more at 75%+ by this point.

Not to mention apple is crippling old devices via the upgrade. Screw upgrading is what many are saying. People have had a enough.
 
I have not seen a test which proves the opposite to what I'm saying. I know quite a number of people who have iPad 2s and I've read article after article, complaint after complaint which would suggest that the vast majority have found their iPad 2 to be slower after the update.

Right.. Articles, after articles.. OK then. We'll agree to disagree.

Some were also saying that about running IOS 5 and 6 on the 3GS (slow, sluggish, battery draining, etc, etc, etc, etc) and I'll let you guess which phone I still use as my main phone till I get the 6+... The 3GS running 6.1.3. Slightly slower than initially, especially in quitting apps, switching apps, starting apps (basically, everything that relates to task switching). But, otherwise AOK.
 
How much Kool-Aide did you drink at WWDC this year? I turned the "advanced Swift sessions" down and spent more time at more pragmatic API sessions.

If you think that all of Apple internally works in Swift to make iOS 8 and the eventual iOS 9, you are due for a big reality check. A lot of the iOS and Mac OS X are still written in K&R C along with -- gasp!! -- x86 assembly to avoid run-time virtual resolvent. Objective-C and Swift are just upper level rappers hiding tread calls. A lot of the iOS and Mac OS X are build outside Xcode!

After an extensive review of Apple outsiders (look it up), Swift is no "magic" language that will accelerate your app development. If anything, you will end up fighting compiler bugs, Xcode IDE bugs and erroneous stack mapping that comes with all first generation compilers and language specifications.

Your choice to run on this frontier like other explorers. The rest of us will passively learn from your mistakes and then build great apps learning from failed Swift app projects of this and next year.

If you really want to shoot yourself in the foot, write an Apple Watch app in Swift. I doubt the processor on that platform can run effectively the very large abstractions that Swift generates. You might as well write it in Python or Perl.
You seem to be falling into the same lack of literacy as others here. Again, I ask where I said that swift was good? The question is irrelevant, and your desire to put your feelings about swift first shows a lack of objective thought that will get in the way of your work. It doesn't matter how you feel. Good players skate to where the puck is going, and on iOS is clearly swift. Being stuck where the puck used to be will show come June. Similarly, I'm sure you hated the useless auto layout features that came with iOS 6, 7, 7.1, and 8. So when Apple increased the number of screen sizes you were completely unprepared and couldn't get your app to support iPhone 6 dimensions in time for the iPhone 6 launch. Users notice such nonsense. The same thing is going to happen to you again if you decide to be a swift laggard as there are swift APIs in the works that users will want.
 
As a developer, this is not good when I'm trying to develop for iOS8-only features. People need to move away from iOS 7 quicker.

The combination of bugs in iOS 8, and the fact that it required WAY too much space, really is slowing adoption.

I hope with iOS 9 we'll see it more at 75%+ by this point.

Unless iOS 9 supports the iPhone 3GS or the iPhone 4, I won't be upgrading.
 
You seem to be falling into the same lack of literacy as others here. Again, I ask where I said that swift was good? The question is irrelevant, and your desire to put your feelings about swift first shows a lack of objective thought that will get in the way of your work. It doesn't matter how you feel. Good players skate to where the puck is going, and on iOS is clearly swift. Being stuck where the puck used to be will show come June. Similarly, I'm sure you hated the useless auto layout features that came with iOS 6, 7, 7.1, and 8. So when Apple increased the number of screen sizes you were completely unprepared and couldn't get your app to support iPhone 6 dimensions in time for the iPhone 6 launch. Users notice such nonsense. The same thing is going to happen to you again if you decide to be a swift laggard as there are swift APIs in the works that users will want.

We got it you think you know all about software development.
You are what in HS, at best college. Either way you do not know anything about the real world.
You clearly know ZERO about software development yet you seem to think this is how it works.

Do you know how far behind we are if we avoid going to swift in terms of being able to develop. VERY little. It would set us back basically a few weeks to get up to speed at most. And during those few weeks we are just slower.
Right now there is little reason to learn to use it or more an existing project into the code base. While Apple "CLAIMS" that they can work side by side reality is not so much. Big time when you have large complicated projects. Example of crazy stuff in apple documentation that we have done. Apple says never move the 0,0 point on a scroll view yet if you have to move that scroll view and have things link to things outside of it Apple official solution is to change the 0,0 point on a scroll view. I kid you not. Problem is when you have to implement things like that (which is an Apple solution) things get glitch when you try to make it play nice with something new.

The larger and more complex things are the less you want to jump over to latest IDE as who knows what little things changed under the hood that you are using.

But hey you never maintain existing software that pulls a lot of money.

But hey you know everything clearly I am wrong. Never mind the fact I do software development for a living and paid pretty well for it. Never mind the fact there are several other professional software developers telling you the same thing. I mean you have never done any of it for a living at at most played in coding and at best done some in school. Never worked on a team in the real world or had what I call a grown up job.
 
We got it you think you know all about software development.
You are what in HS, at best college. Either way you do not know anything about the real world.
You clearly know ZERO about software development yet you seem to think this is how it works.

Do you know how far behind we are if we avoid going to swift in terms of being able to develop. VERY little. It would set us back basically a few weeks to get up to speed at most. And during those few weeks we are just slower.
Right now there is little reason to learn to use it or more an existing project into the code base. While Apple "CLAIMS" that they can work side by side reality is not so much. Big time when you have large complicated projects. Example of crazy stuff in apple documentation that we have done. Apple says never move the 0,0 point on a scroll view yet if you have to move that scroll view and have things link to things outside of it Apple official solution is to change the 0,0 point on a scroll view. I kid you not. Problem is when you have to implement things like that (which is an Apple solution) things get glitch when you try to make it play nice with something new.

The larger and more complex things are the less you want to jump over to latest IDE as who knows what little things changed under the hood that you are using.

But hey you never maintain existing software that pulls a lot of money.

But hey you know everything clearly I am wrong. Never mind the fact I do software development for a living and paid pretty well for it. Never mind the fact there are several other professional software developers telling you the same thing. I mean you have never done any of it for a living at at most played in coding and at best done some in school. Never worked on a team in the real world or had what I call a grown up job.
That's a lot of long rambling drivel, but let's address the last paragraph. Neither you nor anyone else who has commented here has given any evidence of being a professional programmer either by citing your works (which apparently nobody will buy if they get one bad review) nor by showing an understanding of how to make money in software development. Your reasoning is almost entirely emotional (I don't like teh swift!!!!) and full of contradictions (I'm afraid to learn swift but I could do it in a week I swear!!!!).
 
Judging by how much it fudged up my iPad it's not an upgrade and the increasing number after iOS X is the extent of the lag and bugginess level.
 
That's a lot of long rambling drivel, but let's address the last paragraph. Neither you nor anyone else who has commented here has given any evidence of being a professional programmer either by citing your works (which apparently nobody will buy if they get one bad review) nor by showing an understanding of how to make money in software development. Your reasoning is almost entirely emotional (I don't like teh swift!!!!) and full of contradictions (I'm afraid to learn swift but I could do it in a week I swear!!!!).

Just keep believing that. I will sit on the fact that the apps I work on have made the company over 300k+ this year in revenue. I have more important things to deal with that try to prove to high school know it all that I do this for a living.
Get back to me when you get your first grown up job.
BTW I never said I was afraid to learn Swift. I said it is not worth my time right now. It is meh. It just another syntax to learn and provides a few tricks. To any professional programmer that langue is mostly syntax. The key part is knowing how to properly design something, know how to think threw the problem ect. and how to execute it. Programming language each have their pluses and minuses. It is then about choosing the right tool for the job. Professionally I have programmed in 5 different ones.

I can spot out the professional developers in this thread. It is not that hard. Big time if you do it for a living.

As for why none of us want to provide you with anything. We rather not deal with a negative review full of FUD. Would it sink the App no. But rather not have lies out there either.
 
My Air is at 8.1 and it's ridiculously smooth and fluid. I am not sure what's the difference between my iPad and your iPad, but that certainly is not the iOS issue.

The issue is you don't notice dropped frames and I do. The same way as some people can't tell between 30 and 60fps.

Visit a webpage in Safari, tap on the address bar and keep an eye on the animation as the address goes gray and slides left to reveal the full site address (keyboard slides up at the same time).

The address as it slides left is sluggish and not smooth. On iOS 7.1.2 it's uber smooth.

It's there. I've tried it on demo iPads and my old one and did it. It's there, it's real. Perhaps the FPS is acceptable to your eyes, it certainly isn't to mine and not when I've come from something smoother.

There is also a noticeable delay in the keyboard when typing, it's nowhere near as smooth and responsive as iOS 7.1.2 and the five finger pinch to go home has a split second delay that makes it feel slower and the animation can sometimes stutter right at the end of the animation as the apps fly on screen.

As I said, your eyes don't see it. Mine do.

Every. Single. Year.
 
Last edited:
Just keep believing that. I will sit on the fact that the apps I work on have made the company over 300k+ this year in revenue. I have more important things to deal with that try to prove to high school know it all that I do this for a living.
Get back to me when you get your first grown up job.
BTW I never said I was afraid to learn Swift. I said it is not worth my time right now. It is meh. It just another syntax to learn and provides a few tricks. To any professional programmer that langue is mostly syntax. The key part is knowing how to properly design something, know how to think threw the problem ect. and how to execute it. Programming language each have their pluses and minuses. It is then about choosing the right tool for the job. Professionally I have programmed in 5 different ones.

I can spot out the professional developers in this thread. It is not that hard. Big time if you do it for a living.

As for why none of us want to provide you with anything. We rather not deal with a negative review full of FUD. Would it sink the App no. But rather not have lies out there either.
Well well. People can judge for themselves based on the facts whether you are a pro or not

-by your own admission you cannot solve a simple scrollview issue
-you still can't solve it with Apple's help
-you cant provide one single example of your work and hide behind anonymity
-you are certain swift is 'meh' yet you admit that you can't actually use it
-you are unable/unwilling to learn a new language, which by your own admission a pro could do easily
-your stated revenue, which is no doubt exaggerated, is peanuts
 
You seem to be falling into the same lack of literacy as others here. Again, I ask where I said that swift was good? The question is irrelevant, and your desire to put your feelings about swift first shows a lack of objective thought that will get in the way of your work. It doesn't matter how you feel. Good players skate to where the puck is going, and on iOS is clearly swift. Being stuck where the puck used to be will show come June. Similarly, I'm sure you hated the useless auto layout features that came with iOS 6, 7, 7.1, and 8. So when Apple increased the number of screen sizes you were completely unprepared and couldn't get your app to support iPhone 6 dimensions in time for the iPhone 6 launch. Users notice such nonsense. The same thing is going to happen to you again if you decide to be a swift laggard as there are swift APIs in the works that users will want.

This is turning into a fun thread. If you really want to follow the hockey analogy, then the slapshot that Apple did with Swift is missing its target. The momentum towards Swift even inside Apple has lagged. This is why the Warch SDK has been delayed.

They are finding that the code base they need to manage in the App Store is not taking kindly to this. As far as "other sized devices" UI changes happen when the devices become real. Coding toward unannounced and unsupported products is a waist of effort without focus.

Looking forward to you resume passing across my desk. I'd interview you for amusement just to see what flavor of Kool-Aide you drank.
 
Well well. People can judge for themselves based on the facts whether you are a pro or not

-by your own admission you cannot solve a simple scrollview issue
-you still can't solve it with Apple's help
-you cant provide one single example of your work and hide behind anonymity
-you are certain swift is 'meh' yet you admit that you can't actually use it
-you are unable/unwilling to learn a new language, which by your own admission a pro could do easily
-your stated revenue, which is no doubt exaggerated, is peanuts

Umm that simple scroll thing I was talking about. It did not involve me contacting Apple directly. IT IS IN APPLES OWN DOCUMENTATION. That what you find when you read documentation. I found that solution by looking into the documentation as it was not doing expected behavior. Btw not some simple thing. It was us doing something unexpected. It was not behaving as expect or should.
Speaking of someone complaining about literacy issues. I suggest you learn them because clearly you can not do that.

Like another person said I look forward to your resume coming across my desk. I would interview you then put you in your place when you do the know it all stuff. You really have no clue what it takes to be a real developer. I am done dealing with you. You are nothing more than a high school know it all from what I can tell and I have a strong feeling I am not the only one who believes that.

Come one what do you do for a living? What is your big boy job?
 
You aren't much of a developer if you don't appreciate the benefits to devs of iOS 8- universal storyboards for iPhone / iPad, adaptable UIs, many new APIs including UIAlertController which is much better than the UIActionSheet and UIAlertView classes it replaces, etc. Sure, Apple did a good job making a lot of stuff deploy back to iOS 7, such as Swift (which I assume you aren't going to use for 3 years), but that doesn't mean there are no benefits to going iOS 8 only. Obviously everybody's case is different and some, such as yourself, will prefer to spend time testing on obsolete OSes instead of implementing the latest APIs. Suit yourself, the users will decide.

Wow that's a little bitchy, don't you think?
 
Can the "skills" measuring contest stop?

Neither side is going to win this little debate if the gent would like to code for iOS 8 only that's on him and his employer if he/she has one. Yes he's over stating his skills and benefits of the new OS, we've all done it it's nothing new but calling him out in a public forum will only harden his resolve to be correct.
 
No one is going to own up to any published App with the level of hostility you've been showing contributors.
If I said what my Apps were I'd fully expect some 1 star reviews to pop up tomorrow on my radar and I'd have a pretty good idea of who and why.

I don't know what you've been smoking, dude, but you clearly aren't an App developer if you think limiting your labor to 55% of iOS users is sensible.

You've been telling folks on here they aren't any good as developers because they are supporting 2 iOS versions.
That actually takes more work, more development experience, skill and know how that supporting just 1.
"Doing a great app for 55%"....? Eh?
A great App requires a great idea and excellent execution. Not a whole new suite of new API's.
So unless your App is targeting new software or hardware features from September you don't need to limit your App to iOS8.

You just want to bully users, still on iOS7, into upgrading.
Just as you've been posting bullying comments on this forum.



Polemic isn't:

To my post:


or "nomore" 's post:


or "G4DP" 's post:


or "CFreymarc" 's post:


Be a sweetie and be nice to the other folks on here.
Stick to the facts and stop beginning your statements with put downs.
Get someone to give you a hug too, I think you need one.

My view on "Proline" is he (and yes it is a "he") is typically of newbies into the developer scene. They make the mistake the most publicly promoted technology is where the market goes and hops on the band wagon. Anyone else that casts doubt of the song the band's playing gets harsh criticism.

Developers are a critical bunch where aesthetics takes a backseat to function. When in the Apple camp, that is a tough branch to walk on around very aesthetic driven marketing types.

From my industry experience, here is my guess on who Proline is:

1) Developer with less than four years experience on the iOS
2) Moved into coding as a second phase of their career with an initial background in either marketing support or technical support.
3) Has moved from a large company of over a thousand people to now small group efforts where his ad hominem comments backfires hard and quick.
4) To dwell further, a recent significant loss in his personal life be it loss of a family member or a close friend; it could have led to fiscal loss resulting in the change in career.
5) The one at parties who laughs when someone expressed a recent problem or tragedy.
6) Owns a cat. (I have reasons for this one.)

This guy is definitely no Voice of Reason.

----------

You aren't much of a developer if you don't appreciate the benefits to devs of iOS 8- universal storyboards for iPhone / iPad, adaptable UIs, many new APIs including UIAlertController which is much better than the UIActionSheet and UIAlertView classes it replaces, etc. Sure, Apple did a good job making a lot of stuff deploy back to iOS 7, such as Swift (which I assume you aren't going to use for 3 years), but that doesn't mean there are no benefits to going iOS 8 only. Obviously everybody's case is different and some, such as yourself, will prefer to spend time testing on obsolete OSes instead of implementing the latest APIs. Suit yourself, the users will decide.

Quite honestly, I would not be surprised if Swift in its current from is phased out in three to four years. Whatever they call Swift before the decade is out will have better syntax and backwards compatibility. K&R C is forty years old now this week and is the most widely adopted language out there for compiled code.

If Apple does make the mistake of Swift-only API's, most developers will place an Objective-C wrapper around it and implement their own protocols if needed.

To think of it, I can see making an "Unswift" library on GitHib allowing developer to incorporate Swift only APIs into existing Obj-C apps complete with redone protocols.
 
Last edited:
Umm that simple scroll thing I was talking about. It did not involve me contacting Apple directly. IT IS IN APPLES OWN DOCUMENTATION. That what you find when you read documentation. I found that solution by looking into the documentation as it was not doing expected behavior. Btw not some simple thing. It was us doing something unexpected. It was not behaving as expect or should.
Speaking of someone complaining about literacy issues. I suggest you learn them because clearly you can not do that.

Like another person said I look forward to your resume coming across my desk. I would interview you then put you in your place when you do the know it all stuff. You really have no clue what it takes to be a real developer. I am done dealing with you. You are nothing more than a high school know it all from what I can tell and I have a strong feeling I am not the only one who believes that.

Come one what do you do for a living? What is your big boy job?

So what your saying is you didn't read the documentation beforehand? Shocker

----------

Wow that's a little bitchy, don't you think?
Nope, when you claim to be a developer but are ignorant of the benefits of dropping obsolete OSes as Apple does, you deserve a clear rebuke.
 
So what your saying is you didn't read the documentation beforehand? Shocker

----------


Nope, when you claim to be a developer but are ignorant of the benefits of dropping obsolete OSes as Apple does, you deserve a clear rebuke.

What is obsolete and what is the standard to measure obsolescence?
 
So what your saying is you didn't read the documentation beforehand? Shocker.

And yet again you show how little you understand development and clearly you do not even have a clue what it meant by documentation.

https://docs.oracle.com/javase/7/docs/api/

Get back to me when you read that entire thing. I can promise you never will nor does any developer.

https://developer.android.com/guide/topics/renderscript/index.html That is androids.

It more hey this class is not working as I expect or I need to find something that does X to this object. Let me go look at this object to see if there is anything out there that solves it for me. But now I have a feeling you degraded to trolling.

Again what do you do for a living?

I am pretty sure I called it a while ago.

----------

Wow that's a little bitchy, don't you think?

I think it is sad. He clearly is not a developer and has ZERO clue what it takes to be one. He has drank the koolaid hard core. Those people I have watch be shown the door more than once.
 
What is obsolete and what is the standard to measure obsolescence?
Any iOS lower than 7. You'll note that Apple does not have a single app with iOS 6 support, even the simple WWDC app requires iOS 8 in fact. While the self-styled 'professionals' here are jerking off trying to work around old bugs for the benefit of the 5%, Apple is making apps that delight the other 95%, often using the latest APIs. Oh, and making $6-10 billion a quarter vs. the exaggerated $75,000 that Timeless claims to make.

----------

Again what do you do for a living?
I'll tell you once you tell me what you do. It sure as heck isn't software development if you haven't mastered the scroll view. I'll give you a hint- I don't go around claiming to be something I'm not.
 
[/COLOR]
I'll tell you once you tell me what you do. It sure as heck isn't software development if you haven't mastered the scroll view. I'll give you a hint- I don't go around claiming to be something I'm not.

That scrollview I was referring 2 was an odd ball case. Where I was controlling one scrollview from another.Apples own documentation explains that they have issues with that. It requires an odd ball solution that goes against what their documentation states as it causes the scroll view to want to go to 0,0 when you have things linking around.
 
Last edited by a moderator:
Just keep believing that. I will sit on the fact that the apps I work on have made the company over 300k+ this year in revenue. I have more important things to deal with that try to prove to high school know it all that I do this for a living.
Get back to me when you get your first grown up job.
BTW I never said I was afraid to learn Swift. I said it is not worth my time right now. It is meh. It just another syntax to learn and provides a few tricks. To any professional programmer that langue is mostly syntax. The key part is knowing how to properly design something, know how to think threw the problem ect. and how to execute it. Programming language each have their pluses and minuses. It is then about choosing the right tool for the job. Professionally I have programmed in 5 different ones.

I can spot out the professional developers in this thread. It is not that hard. Big time if you do it for a living.

As for why none of us want to provide you with anything. We rather not deal with a negative review full of FUD. Would it sink the App no. But rather not have lies out there either.

Not having a go because I've enjoyed your posts, and while I don't know if you're a legitimate developer or not, that's not my place, I just know that I wouldn't expect a professional to react with such an overly defensive tirade. Then again, this place can be frustrating.

And for the record, I have a "grown up job" and just thought I'd comment in passing. Don't rise to troll bait to prove yourself though.

However, Proline is wide of the mark if he believes developers should focus on iOS 8.

I'm not a developer and even I understand that the latest OS and hardware isn't the main target simply due to the larger install base of "outgoing" devices. Sure the iPad Air 2 chip is powerful by the iPad Air, iPhone 5s and iPad Mini Retina all have year long install bases and are most importantly still on sale.

No new iOS device ever hits it's peak within a year. Not now.

The iPad Air 2 won't have been stretched by any means by developers when it's replaced and the same rings true for the current generation Air and Retina Mini. The speed that these devices are updated hardware wise makes it impossible for developers to focus on the newest gear only.

Apple themselves are guilty of the very thing Proline mentioned with their iWork apps on iOS 8.

Numbers and Pages are iOS 8 only, but thankfully Microsoft made Office for iOS 7 onwards. There's no need to force users onto the latest OS, especially when it's a bug ridden mess.
 
Last edited:
You make some valid points but you sound like one of the very people you speak about. I don't know if you're a legitimate developer or not, that's not my place, I just know that I wouldn't expect a professional to react with such an overly defensive tirade.

And for the record, I have a "grown up job". Don't rise to troll bait to prove yourself.

However, Proline is wide of the mark if he believes developers should focus on iOS 8.

I'm not a developer and even I understand that the latest OS and hardware isn't the main target simply due to the larger install base of "outgoing" devices. Sure the iPad Air 2 chip is powerful by the iPad Air, iPhone 5s and iPad Mini Retina all have year long install bases and are most importantly still on sale.

No new iOS device ever hits it's peak within a year. Not now.

The iPad Air 2 won't have been stretched by any means by developers when it's replaced and the same rings true for the current generation Air and Retina Mini. The speed that these devices are updated hardware wise makes it impossible for developers to focus on the newest gear only.

Apple themselves are guilty of the very thing Proline mentioned with their iWork apps on iOS 8.

Numbers and Pages are iOS 8 only, but thankfully Microsoft made Office for iOS 7 onwards. There's no need to force users onto the latest OS, especially when it's a bug ridden mess.

Yeah I should of just ignored him earlier on and I know I got raised by his bait.
As for the rest,
Updating to iOS 8 only and focuses only on that is not an imported as you think as much as you think. First thing is you make sure your stuff still works as expected on iOS8.
Now going over to say making your App iOS8 only comes down to is there a reason 2. Does iOS8 bring anything new to the table to make it worth it. It is all a balancing act. It comes down to is worth the time and effort.
 
Safari and App Store crashing all the time? That's what it was like for me running iOS 5.1 on the iPad 1.

I don't recall any App Store crashes, but Safari often crashes with just one tab, so I usually use Chrome. Fortunately the stock email app is solid.
 
Now at 61%

From my App analytics I can see that iOS8 is now around 61% of users.
I posted a reply here on Nov 12th saying it was at 54%
So that's +7% in 20 days.

We could see it hit 70% by the new year at this rate.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.