Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Seeds First OS X 10.11.6 El Capitan Beta to Developers
- Thread starter MacRumors
- Start date
- Sort by reaction score
Let's hope it snows then.😉
[doublepost=1464296428][/doublepost]
App store opens but no content. In iTunes, app updates appear but the app store does not have any content. What's that all about?
SaxnFlutman
macrumors member
I'm sorry just to call you out, but why rail on someone with the bogus, straw man argument, that we ought to be happy and content because Apple is better than Windows? This has zero to do with the issue of OS's never being fully stable, and then a new one is released. If someone was pointing out some problems here in America, would reading someone the riot act, because he's obviously never lived in North Korea, make any sense whatsoever?
I've been a Mac user for well over 20 years, and I've seen quality control, and ease of use go steadily downhill. Things should be getting better, not worse, and it sure seems to me that the Apple developers are so eager to add more bells and whistles and revamping major applications (iTunes, Safari, Mail, etc.) that they no longer work as intuitively nor with as much stability as they used to. I'm still using Snow Leopard, and know I need to upgrade, but I have no idea how far up the ladder to go. I don't need a basket full of bugs, nor want to take time & energy away from my work, to re-learn how to use iTunes, & Mail, & other basic apps.
Does it really make any logical sense to be still working out bugs with the current OS, right up to the release of yet another new one, and repeat the same process all over again? Why not get one to just work, without a segment of users having to endure even catastrophic situations, and let it ride for even a few months, before putting attention on yet a new one? Why do we need constant updating anyway? I'm playing on pretty much the same instruments that I have for the past 40 years, and they work just fine. Why would I want to spend lots more time, constantly getting new ones, that may not be as good, when the ones I have work just fine?
I'm using iTunes 10.7, and it works great, does everything I need, and so why the hell should I have to learn a completely new iTunes, that's just more complicated, and maybe buggy? How is that progress? Progress would be to only release updates when they know they're bug-free, don't make using apps more complicated & less reliable, and know that their users are happy doing what they need, trouble-free....
I agree. "It just works" is now something of a cruel joke. But I suspect as someone else mentioned, it's simply as a result of the push to generate a steady stream of revenue coupled with tight deadlines.
MrNomNoms
macrumors 65816
Personally for me I like the new UWP look and feel but Microsoft have let themselves down with their 'half assed is good enough' approach to UI development with no attempt in the updates to actually fix it up or at the very least announce some sort of roadmap to bring about continuity in UI design for at least their own products and the 'out of the box' look and feel of Windows 10. That being said, once again it appears that Microsoft moves forward but never having a coherent plan given that even within UWP there are fractures showing because Microsoft doesn't seem to want to fix Windows but rather they base UWP on top of Win32 so you inheriting all the bad design decisions not to mention the mixture of UWP feel and MFC such as if you're running an application then save a file you have a MFC save dialogue come up. It appears that Microsoft is chronically addicted to win32.
And if you did any software development you would know that is absolutely impossible. You can never make software bug free because there is always going to be some bug some where so it'll be a never ending bug fix feast and no new features, improvements or enhancements would ever be made. Keep your expectations realistic.
The problem with Windows is that they try to fix Windows whilst keeping within the confines of their existing structure for the sake of backwards compatibility so in reality they'll never be able to adequately fix the problems without first having to accept that there are fundamental flaws with Windows and secondly a willingness to break compatibility. For all the flaws of Apple and OS X they did make the best move 16 years ago when they broken compatibility with MacOS 9 and created MacOS X and I think part of that is the result of Apple having small teams which forces engineers to really think smart about how to achieve a task where as Microsoft over engineers a problem because they've got so much resources and man power to squander that they belief they can have their cake and eat it too. In the case of win32 I believe that they've convinced themselves that they can move forward and keep backwards compatibility under the mistaken belief that they can engineer their way out of a problem but if Microsoft had smaller teams then you might find that engineers might actually be forced to make tough decisions earlier which would have avoided a lot of what you see today.
Reminds me of the 'back to the Mac' with Steve Jobs where be pointed out the fallacy of touch screens and heck, I've got a Surface Book and I must have used the touch functionality maybe 1-2 times if for no other reason that curiosity. My sister has a touch based laptop for her work and again she has never used the touch functionality because as she said, "why would I....I already have a mouse". I think what Microsoft was hoping on was that touch would be the 'next big thing' and end users would upgrade their hardware to get touch functionality which would in turn drive OEM sales as well as Windows units being sold as well (via OEM bundling). Then again this has been the same approach Microsoft has taken in the past where new versions become more bloaty which in turn propels people to upgrade their hardware which in turn drives more Windows OEM sales. In the case of Apple I think they're doing the right thing although I do disagree with whether the iPad Pro is meeting a need or whether it is a reaction to what management believe is a long term trend but actually might turn out to be more of a fizzer.
I think the problem is also bigger than that given that if the Windows 10 Feedback tool is any indication on the kinds of feedback that OS X engineers receive then it appears that there must be a lot of time wasted sifting through crappy feedback that actually go no where or ultimately the result of the end user doing something stupid. As much as I understand the need for 'public previews' to get the base pumped up and excited I still believe that they need to select a small group of testers who can actually write coherent bug reports and have enough technical knowledge to give meaningful feedback to OS X engineers. Not only do Apple developers need to scale back the features they add they also need to improve the base of testers so that meaningful feedback can result in a prompt resolution to problems.
Last edited:
gmanist1000
macrumors 68030
Clearly you didm't read my post fully before giving your "expert" opinion. I'm getting tired of listening these nonsense arguments about bugs being never fixed from lazy developers like you. There are many software developers who fix bugs in their software after a few iterations and their softwares work fantastic. So stop preaching this nonsense software development philosophy of yours! Apple too fixed bugs in minor updates following the major release in the past (until Mavericks). It's only after Yosemite this nonsense has started at Apple that they don't want to fix bugs but release a new nuisance every year. Besides there are not many groundbreaking new features coming in every OS X release these days. In past Apple shipped more features in OS X then they do now, so your argument has no merit.
Every release of OS X up to date has contained bugs. I have no idea why or on what grounds you would state that Apple is not fixing bugs since 10.10. I have submitted over a dozen OS X bug reports in the last year, all of them have been fixed.
Again, I have no idea why you would say that. There are TONS of features and enhancements every OS X release. And 10.11 has been a MASSIVE upgrade. Alone the 10.11 to 10.10 API diffs are over a hundred pages long.
grahamperrin
macrumors 601
I find the problem consistently reproducible with at least:
- Lion
- Mountain Lion
- Mavericks
- Yosemite
- prerelease El Capitan.
I have submitted bugs too and even one and half year later and despite the acknowledgements they are still to be fixed. I didn't say that Apple is not fixing bugs but I said Apple isn't making the last version of OS X bug free before realising a new version. And just because APIs are different, it's doesn't mean new features for consumers automatically!
grahamperrin
macrumors 601
For some bugs, years will pass before a fix or supposed fix. Not ideal, but sometimes that's the nature of software development. The best you can do is describe the bug in a way that will make it easily and consistently reproducible by an engineer.