Tim Cook’s decision to get rid of Scott Forstall was shortsight and stupid. Better collaboration my ass.
I don’t. I’d rather have new features and I’m prepared to accept a less stable system because of it.Fair enough. However, I remember showing a friend the iOS 12 beta and they reaction was, "It doesn't really seem different". That didn't make them switch their iPhones though. I believe users want stability over features any day of the week.
But why did it take them this long to see their method was bad ?
If they follow an Agile framework, they can simultaneously announce their major initiatives for the next year while maintaining flexibility to deliver customer value on a frequent and regular basis. Instead, it sounds like they are sticking with very old and inefficient waterfall methodologies. There is a time, place, and use for both.
I wrote a post in the Mac Pro forum questioning how Phil Schiller (and his org) seems to always be let off the hook. Seems to me the software release cycle at Apple is absolutely driven by marketing. Driven by the need to have a big reveal at WWDC and again in the fall when new phones are announced. That’s a problem as it forces the software teams to announce and release things before they’re ready.Microsoft rolls out Windows feature updates on a 6-month cadence with no specific criteria on what goes in... until things are ready. There is absolutely no need to rewrite the entire OS every single year; on the other hand, even if they don't rewrite the source code for the lower-level OS services and subsystem, or the components already built several years ago, everything still needs to be vetted properly. What's abundantly clear is that's not being done.
I don’t. I’d rather have new features and I’m prepared to accept a less stable system because of it.
No thanks, I’d rather have frequent massive updates, and I find already appalling that in the last few years there were very few new features in the ‘big’ yearly update. Who prefers stability don’t have to install them and can wait until they’re stable enough for his needs.
Tim Cook’s decision to get rid of Scott Forstall was shortsight and stupid. Better collaboration my ass.
I'm glad he got rid of him. We don't need the stupid, "You can tell it's a note app because it looks like an actual note" BS.Tim Cook’s decision to get rid of Scott Forstall was shortsight and stupid. Better collaboration my ass.
Apparat from the os changes that needs to be done to accommodate next years (almost certain) 5G modem inclusion, but jea basicly I agree with youI'd like to see Apple continue putting out bug fix releases, though I'd like to see Apple delay any major updates until 2021. Clean up the code so it's not buggy, make it more clean & efficient, and then put in new features.
Honest question to developers: what's SwiftUI like? Easier/harder, better/worse than UIKit & AppKit? If SwiftUI's easier & better, I'd like to see Apple also port more of the OS & App code to Swift.
Didn't they already do that after buggy iOS 11?
How quickly organizations forget.
OS X development has been a disaster for ages. Remember when they announced Snow Leopard? Or had to scrap the iPhotos app, or re-wrote iMovie in a way that wasn't even fully backwards compatible? Apple has always been about marketing, lick-ability, and smoothness. Often Apple will compensate poorly written software with over-spec'd hardware (e.g. check out how well an HDD works to boot OS X).I said it ever since 2012(?) that macOS releases cannot be annual because too many “features” are added just for marketing, current bugs don’t get fixed, only bugs in the “new features” are fixed (sometimes) and then the core is slowly rotting away. Now this same problem is happening to iOS.
I can’t believe Apple are only realising this now... it seems like such an obvious issue. This new “build all features at the start and only switch them on when they’re ready” strategy is welcomed, but it’s what other software engineers have been doing for years??
Naturally, but possibly not everywhere. Microsoft revamped their development process following the Vista debacle, and while they're heavily invested in testing, not only are some things not written test-first, I've heard that some (very) legacy configs don't even have tests.Some comments I saw suggest TDD. I'm sure Apple is using some form of unit testing as this has been industry standard since the 90s; Otherwise iOS and MacOS would have fallen apart many years ago.
Apple is undergoing a massive culture shift in 2019. Listening to customers, fixing the MBP, pricing iPhone 11 right and now hopefully stabler software from next year.
Especially for macOS this is true. Apple please stop torturing us with mew Emoji, Animoji and XYmode releases. I don't care about your "now with 64bit only - your old software doesn't work anymore" approach. I don't want to be forced to notarize apps - by the way does this mean any application used by HongKong demonstrates won't be notarized?I'd be very happy with a non yearly update and more to an update as needed model. I would imagine that would result in a much better experience for all.
Don’t worry, we’ll all be using cloud-based OSes in a few years. Pay your subscription fee and access the delicious dog food. The Future — yum yum.Just stop with the huge yearly updates. Just add features when there ready. Maybe announce a year long roadmap of features, but slowly add them over a year, instead of trying to rush everything for September. Also, put macOS back on a 18 to 30 month upgrade cycle
Can we return Catalina? Embarrassing release.
I never had any issues with iOS 13. Mac OS Catalina on the other hand..... 😭😭
iOS 13? What about Mojave and Catalina. Disasters.
Mojave for me been great from the beginning...