It's obvious the IOS code base has gotten more complex and therefore software bugs are to be expected. It's not the bugs I look at, but the response to the bugs, and imo, Apple addresses issues these days with some fervor.
As I stated above, it's the response to the bugs, not the bugs themselves.
How the f/t bug came to be is less relevant than how it was addressed, imo. It's easy to say it should have been caught early on, but if that were the case for many of the issues that plagued windows in the past, Microsoft would have learned from it's mistakes and not have to patch Windows 10. You don't really know if Apple "just doesn't care" or a bug that slipped through what is probably some complex scenarios that was overlooked in testing. Overblowing the issue doesn't help either.
Apple, Microsoft, Samsung (sending your pictures to random people...comes to mind and batteries blowing up) don't need a wake-up call. Software development and bug remediation is always a developing process and hopefully these companies do adjust their processes as time goes on. But calling people out (if they are not part of the solution they are part of the problem) for differing opinions and making some assumptions on an anonymous internet board doesn't help either.