|
Normally I have little say nice about Microsoft, but the one thing I agreed with their development strategy was to release the update/upgrade after it was ready rather than on some predetermined date. it pissed customers off, but at least they got a less terrible release that way. I know from experience working with software companies that trying to make deadlines that are chiseled into stone while marketing keeps agreeing to new features up to the end and management okays same, well that is a recipe for disaster. You almost never heard them agree to push a promised feature to the next development cycle. I’m not a programmer, but I watched those poor folks working around the clock the last several weeks before the final release trying to deliver the undeliverable. While it was usually the position of management that the fault was due to the programmers not getting the work done in a timely fashion. They rarely looked into the mirror and pointed the blame at themselves, where is really belonged. I don’t know wherein Apple's development issues lie, but I know they are not perceived and they need to be fixed. This has been happening a lot in the past several years. One of the macOS releases a few years ago had to have constant updates all year long because it was so bad. So bad in fact the Apple promised to focus on getting things right before tackling new features. A promise they never kept IMO. I for one, and I know other long time Apple users (as in over 30 years of using Apple software and hardware) who will never again be quick to adopt their new releases/updates. They have a systemic problem that needs to be fixed...
|