when you say 'many users'... how many exactly? and where are getting your information?
ALL new os'es have bugs, and may have incompatibilites with existing software; we've been discussing these things on this forum with every new OS since i've been here (2010). so yes, SOME users have issues, and... some don't.
as usual, even tho it makes more sense to ask for help here, and discuss issues, some people are happier whining, making 'absolute' statements based on their personal experiences, and stating facts that actually lack proof.
it's endless.
It is true that all software has bugs. But, quality assurance, skilled programmers, and a lot of testing should get them shaken out. Software code is not as refined and carefully written as it used to be. Granted part of the problem is that the tasks being attempted are complicated and numerous. Computers are expected to do a lot more now than they used to. And, the operating systems are extremely complex compared to what they used to be. And, once sloppy code and procedures get into the software, they tend to take a while to reveal themselves as needing fixed. Often it's when you add another feature, that you find a conflict with something else that was previously implemented. Compared to finding something old that's causing trouble, it's far easier to start at the beginning and build fresh if your programmers are skilled enough and you want to eliminate all bugs. It's time consuming, and takes careful thought, and you don't release annual updates.
Imagine if today's programmers had to work to the perfection level of the programmers in the 60's, 70's and early 80's. There was no concept of we'll release a service pack or an annual update. You wrote it, you better get it right, because that's how it was going to be forever. I remember using computers that had their operating system encoded into ROM. There was no service pack. That computer's operating system would never be updated or patched. It better be pretty close to perfect before it went into mass production, or you were going to get a lot of paperweights back and no future sales.
The great thing about those computers, is that every time you turned it on, it was like a factory fresh install. Nothing lingering from yesterday or last year.
Today's programmers do have it hard. They have to write in several different languages, implement ideas that are new, and it is complex. We are mere humans, and make mistakes. But, at the same time, we have unfortunately gotten into a rush to market, and fix later mentality. And, that's not just Apple, it's the whole industry. You have to beat your competitor to market. You have to keep up. You can't drag your feet pouring over every line of code until it's perfect. You have to get it good enough, get it out there, hope for the best, and fix it later.
It's clear that companies like Apple are aware that they are releasing software that has bugs. Many times there has been a gold master issued and public release with a beta of a 0.1 service pack / update being announced or released the same day or next day. They know they are releasing code with bugs at the moment they release it. Unfortunately, as a society, we accept that. And since we accept it, they do it. That's not an option or luxury that any programmers in the very early 80's and older enjoyed. Yes, as we finally got software on floppy disks, we did occasionally get updated versions. But, prior to that, the first release had to be perfect, or you were going to sink.
We didn't used to accept a buggy release. If it glitched on us, it was a huge problem, because it was in our hardware. Firmware. And back then there wasn't a do it at home flashing process to reprogram firmware with a patch. So, if we tried to use the "operating system" or even "software" (which by today's standards was also technically "firmware" in pluggable form), and if it glitched, we considered it done, over, trash, and discarded / returned it. There was no wait for a patch, because there would never be a patch. That is a new concept.
When you release software, you should believe it is perfected. You should never release a product that you are already expecting to fix. Would we buy a tire that we knew had problems that needed worked out? Hey... the manufacturer is working on a fix, they'll get it to me in a month or so, I'll just use the tire like it is until they release the update, then I'll get it patched????
I realize it's hard. But, no matter what industry you work in, you should always have the goal and mind set that you don't release anything that isn't actually ready and perfected. We are humans and make mistakes. So errors happen. But, the person releasing the product should believe in their heart and mind that they have perfected the product and believe that it does not need any repairs at the time it is released to the market.
Software is an industry that enjoys an extremely luxurious position. Companies can release software that they are fully aware is not "finished" and not "perfected" and just issue a service pack later. They release the final product at the same time that they are already working on the first of many service packs for that product. That's not a luxury that many other industries enjoy. I have people here doing work on my building at the moment. I had them come in, get their measurements, go back and design everything on paper, then build everything to my specifications and to the specifications of the building, and come on site afterwards and deliver and install. And, I'm supervising. It's done right and perfect the first time or not at all. And, they've got it. They arrived on site with all the materials prebuilt, and ready to go in, and it's going together as smoothly as a puzzle with the pieces numbered. Perfect delivery, perfect installation, and I wouldn't accept anything less. If they had to come out here and rework anything, I'd send them back to do their engineering over again. There is no fix later, it is fixed before you deliver.
I'm not against Apple, or any other company. I am just a call it as I see it person. I do like Apple, and I do like Microsoft, and several other companies as well. I will stand and support them, but I will also freely admit when I see a problem as well. I don't defend imperfections, I acknowledge them. That doesn't mean I'm against any of them. I'm just acknowledging what I see.
