It's wild how much of an effect this poor optimization has on my overall impression of the product.Imagine if Avie was in charge of this OS. He wouldn’t have shipped the home view app drawer that scrolls at 10fps.
It's wild how much of an effect this poor optimization has on my overall impression of the product.Imagine if Avie was in charge of this OS. He wouldn’t have shipped the home view app drawer that scrolls at 10fps.
I am, though I haven’t yet installed this second beta. But IMO, any 1.0 software is essentially a beta version, chock full of bugs and incomplete features. There isn’t much difference between an official beta and a release build this early in a product’s lifecycle. I have detected some differences between the first 1.1 beta and 1.0.2 release in terms of Safari’s partial instability, which oddly I haven’t seen again since the first day of 1.1. I’m guessing this second beta rolls 1.0.3 updates into the beta along with additional bug fixes for 1.1 features since you cannot install 1.0.3 once you’ve updated to the beta.Imagine buying an Apple Vision Pro for yourself, taking it home, and then running beta software on it.
You're technically not supposed to do it on a personal device, yet I wonder how many people on MacRumors are doing this right now.![]()
There’s no such thing as bug free code and no such thing as code being shipped without known bugs. With the complicated software these days with millions of lines of code, it is humanly impossible to have no bugs. On my last major project before I went to contractor status, we had shipping versions with at least 2,000 known bugs, most of them minor but a few with quite high severity but low priority. The latter means that the bug is quite nasty, bug rarely shows up, or is impossible to reproduce. I wouldn’t be surprised if all of Apple’s OS software contains tens of thousands of known bugs, whether they are release versions or not.Seems most software tech these days is released in what I'd characterize as Beta+ state of development. The companies' testers and engineers do everything they can to assure whatever SW is stable and functional, but there's no way they can anticipate all the ways endusers will use and misuse the product, and so there comes a cascade of "updates," to mitigate those unanticipated glitches.