Sometimes I wonder why these people continue to by Apple by the way they constantly complain.
Because after everything whined and not, they still know that the experience is pretty much unmatched as a total package. And, whine is the new cool.
Sometimes I wonder why these people continue to by Apple by the way they constantly complain.
White is not an emulator.Because after everything whined and not, they still know that the experience is pretty much unmatched as a total package. And, whine is the new cool.
And if there is a bug in the release, you people will be the first to complain and complain the loudest that there weren't enough betas. Very sad.
[doublepost=1489697053][/doublepost]
Certainly the most absurd statement I've heard in a long time. Based upon your logic, there shouldn't be any betas as everything should work in the first iteration.
I am myself a developer, and if i'll send a 7th iteration to client with still bugs in it, they are simply going to cancel the contract![]()
You are saying your software is completely bug free? (Or for what matter the environment, tools, and the OS you are using are bug free?)I am myself a developer, and if i'll send a 7th iteration to client with still bugs in it, they are simply going to cancel the contract![]()
Yup, I'm betting the issues are related. I know folks have complained about slow text editing in Safari text fields on comment sites, and I'd bet Safari is using the new text APIs (I mean, I have no doubt). I jumped from 10.9.5 to 10.12, so I really don't know –when– the change really started to be a problem, but –something– is very wrong. I probably should start taking more note of which apps I have performance issues within.more specifically the underlying APIs
Yup, I'm betting the issues are related. I know folks have complained about slow text editing in Safari text fields on comment sites, and I'd bet Safari is using the new text APIs (I mean, I have no doubt). I jumped from 10.9.5 to 10.12, so I really don't know –when– the change really started to be a problem, but –something– is very wrong. I probably should start taking more note of which apps I have performance issues within.
I'd guess that most users on iOS don't see the performance issues because most users are typing with two thumbs… not 60+ wpm on a keyboard, complete with 5+ wpm of misspelling![]()