Yeah I know
. I’m going to upgrade to an SSD soon.
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.
Beta 6
- Thread starter lvanness7690
- Start date
- Sort by reaction score
. I’m going to upgrade to an SSD soon.
Yeah I know
FWIW - I am running Catalina on a mid 2012 15" MBP non retina - and I can't tell the difference in speed vs my 2015 rMBP on Mojave with 4 cores
Not saying that if I compared benchmarks there wouldn't be a big difference - but for practical purposes the 2012 MBP runs really well
2012 MBP's are great laptops and still work like champs and very inexpensive to upgrade
Does yours have an SSD or HDD?FWIW - I am running Catalina on a mid 2012 15" MBP non retina - and I can't tell the difference in speed vs my 2015 rMBP on Mojave with 4 cores
Not saying that if I compared benchmarks there wouldn't be a big difference - but for practical purposes the 2012 MBP runs really well
2012 MBP's are great laptops and still work like champs and very inexpensive to upgrade
Also I agree, I love my 2012 MBP.
Sorry I forgot to add that important part - installed a Samsung EVO 500g SSD about 5 years ago - it was taking over a minute to boot with the HDD (get a coffee and wait) after installing the SSD 15 seconds to boot - incredible difference and easy to swap out the drive.
I bought a new 2015 15" rMBP at the same time and it's great but not really much faster for day to day use (after the SSD) - the 2012 is still great and has all the ports like ethernet, firewire plus a CD drive - SD card reader for my old camera etc
Samsung Evo Drive for 2012
Like fixing breaking Firefox. News and Safari network connection buffering issues. Using News is like watching nothing but a spinning loading wheel on gathering content. Latest iOS News works this is just crap in Catalina Beta 5. Playing content from TV also seems to have a lot of hesitation when you stop, change timepoints.
Yes liked previous beta so much better. Now its looking at the earliest Aug 19th, the previous beta was July 31st. How much time do you need to get it in a better place?
Like fixing breaking Firefox. News and Safari network connection buffering issues. Using News is like watching nothing but a spinning loading wheel on gathering content. Latest iOS News works this is just crap in Catalina Beta 5. Playing content from TV also seems to have a lot of hesitation when you stop, change timepoints.
Yes liked previous beta so much better. Now its looking at the earliest Aug 19th, the previous beta was July 31st. How much time do you need to get it in a better place?
And piles of other stuff, iCloud problems and hanging installs being some of the worst widespread ones. How much time? I’d say they really do need that time to un**** some of these things.
I do feel bad for people who are stuck on an unworkable build, waiting.
With great power comes great responsibility.
But in earnestness, it is not Apple's responsibility only till the point where it is not something of their doing in the first place that they are working to fix.
Things are not so black and white where we can make off-the-cuff statements like that.
Case in Point: I use Rapidweaver and a plugin was not working owing to notarisation issues. Two betas later, the plugin started working. This meant that Apple fixed something in their software that (apart from other things) was also causing the plugin to not work. Nothing the developer of either the plugin or Rapidweaver could do in that case.
It becomes Mozilla's responsibility when Apple makes a change that requires developers to make compatibility changes - this becomes clear to the developers early on and they are usually quick to confirm to their user base that a fix is in the works and will be available by the time an OS releases. So long as that is not the case, all "breakups" are Apple's doing
and the onus to fix that lies with them alone.
I remember not too long ago, Microsoft announced that Windows was the last Windows, that it was going to just update as and when required...So really in 64bit and beyond do we need stupid named operating systems? Why not just update as and when required, so no more silly names like Mojave, High Sierra, Catalina... it should just be Mac OS and be done, so that you are not chasing fixed updates...
Rather focus on the OS fitting the system!! I am sure it would not be that hard to figure out an install tool that verifies each system and only loads what is appropriate for that system, instead of forcing "bloaty" software onto an older device, the Mac OS operating system is tailored for each device, be it Air, Mac Pro, Macbook Pro...
This way if the update breaks the system as is with beta 6+firefox, then a 2 hour recoode is done, in fact if you don't have beta's would firefox have been broken???
Rather focus on the OS fitting the system!! I am sure it would not be that hard to figure out an install tool that verifies each system and only loads what is appropriate for that system, instead of forcing "bloaty" software onto an older device, the Mac OS operating system is tailored for each device, be it Air, Mac Pro, Macbook Pro...
This way if the update breaks the system as is with beta 6+firefox, then a 2 hour recoode is done, in fact if you don't have beta's would firefox have been broken???
You are correct, the legacy Mac OS's are doing more than fine on HDD. I am running Mavericks on this exact 500GB HDD on my late 2008 unibody MacBook and it runs incredible(even when connected externally via USB2.0). Needless to say I did not expect the 5400rpm HDD to perform this well in 2019. I guess a different Mac OS for a different hardware, there is absolutely no way around it.
Last edited:
It is in this instance, because the reason Firefox doesn't work is due to a bug in MacOS.
I'll be so happy if Beta 6 includes RX5700 drivers. I bought one (along with an eGPU enclosure) not realising it was unsupported by macOS.
Catalina is in beta, beta 5, beta 6 was stolen/lost/homework was chewed by the dog... Firefox should work, but Apple goofed the beta 5, something broke...No way Mozilla can do about that...Sadly Apple Inc have given the users the bird so to speak...the fact no single point failure update to resolve Firefox has been published shows just how little Apple Inc cares...As far as Apple Inc is concerned, if they never published another line of code, they would not suffer 1 bit...If you don't like it, there are alternatives.
They likely went with iOS/iPadOS/watchOS/tvOS as priority this year since they share a lot of code. macOS had many issues since beta launch this year and will likely launch after the others this Fall to give them more time to correct the problems. And maybe Apple hasn't released a new beta because of all the issues and everyone talking about them as a way to stop people from having more problems, it gives them time to fix what is broke and released a more polished beta next.
Most years macOS comes out a week after iOS and other OS's. This year though I have a feeling we may see macOS kicked down the road a few weeks. From what I was taught Fall starts Sept. 21 and goes until Dec 21. So when you say Fall it means it can come out anytime between that time, despite what we are used to from Apple a week or 2 after the iPhone show.
Most years macOS comes out a week after iOS and other OS's. This year though I have a feeling we may see macOS kicked down the road a few weeks. From what I was taught Fall starts Sept. 21 and goes until Dec 21. So when you say Fall it means it can come out anytime between that time, despite what we are used to from Apple a week or 2 after the iPhone show.
I sure hope we get the Firefox fix soon. I have classes starting in two days that require Firefox to run properly.
As has been said, the next Catalina beta will fix Firefox. Hmm - let me change "will" to "should"
https://bugzilla.mozilla.org/show_bug.cgi?id=1570451
When that comes is anybody's guess. Should be soon, but if I definitely needed Firefox in two days' time I'd be preparing a backup plan.
https://bugzilla.mozilla.org/show_bug.cgi?id=1570451
When that comes is anybody's guess. Should be soon, but if I definitely needed Firefox in two days' time I'd be preparing a backup plan.
It was Apple code causing Firefox to die.
See this bugzilla thread: https://bugzilla.mozilla.org/show_bug.cgi?id=1570451
Not sure why Apple has taken this long to update the faulty code re Firefox...keep hoping for a fix, days and days, weeks and nada...I am sure it will be fixed...
As far as I can tell, reading between the lines in the bugzilla thing I logged, Apple fixed it pretty much immediately. But we have to wait until they release the next beta (*fingers crossed for today or tomorrow*) until we get it.
Adrian, which begs the question.."Why has Apple taken so long to publish?" After all they can publish an update to change the period in a sentence...so to not publish a vital update so as to prevent Firefox from launching is a tad suspicious..
I don't think they care very much about whether Firefox works or not during the betas. Not enough to push out a special fix. I always hope it won't, but understand that betas may break things I like to use. I download the betas with that assumption. If anything, a few weeks of Safari will make me enjoy Firefox even more when I get it back!