2.46 and OSX64

Hi,

I’d just like to mention that officially, 2.46 isn’t supported on OSX 10.7 and 10.8; but apparently, some have managed to get it working.  As I’m not even remotely knowledgeable in OSX64, I have no way of knowing what is not supposed to work in OSX 10.7 to 10.8. (Though… it *is* Christmas. 🙂 )

Now the question some people are probably asking.  If 10.7 -> 10.8 *aren’t* supported, then why are they being updated to 2.46?

Good question.   [Yes.. let’s watch me squirm for an answer.]

Basically, I done goofed.  With so much vested energy in the release process, it had slipped my mind that OSX 10.7 and 10.8 aren’t supported (as did the non CPU SSE2 issue).  So those affected ‘can try’ 2.46, but it’s unsupported.  Worse comes to worse, you return to 2.40.

I seem to remember writing about how this is an example of technology ‘improving’ (for some definition really) leaving those who use hardware(that still work, mind you) wondering what to do.   [I realize that I can probably ramble on with a diatribe on how technology is seemingly ‘improving’ but it’s still not making our lives any bit easier.  But I’ll just dispense with it. 😛 ]

I apologize for not mentioning this or even fixing this (not sure how I can do that), aside for getting crazily-rich and buying everyone a brand new machine of their choice.  (Yeah… as Kenny Nolan once sang, “I like Dreaming”.)

:ewong

[Standard disclaimer: Everything I’ve written above are my views alone.  It may or may not reflect the views of the SeaMonkey project and its members.]

6 Responses to 2.46 and OSX64

  1. I updated SM on my old mac OSX 10.7.5 (Lion) from 2.26.1 to 2.46 (only to test).
    At starting up SM crashed the fitrst time, but the second time and later on SM opened and I didn’t see further problems. So 2.46 seems to work on it correctly.

    • I’m not an OSX64 user (aside for fiddling with the OSX64 builders), so I don’t know what would make 2.46 not supported on 10.6 -> 10.8. However, that said and despite it not being supported, I’m quite glad that it’s working on your system. Just make sure you do back up your profile just in case.

  2. Just got my copy of the Linux x86_64; all shiny and brand new. No probs with anything, here; thanks ewong!

  3. If you do breaking changes like these, you should have renamed it to Seamonkey 3.0 so nobody would get stuck due to auto-updates.
    I hope next versions will come back in time.
    Thanks.

    • Unfortunately, 3.0 would imply something different; but aside for the changes in platforms’ minimal requirements and some fixes, I’m not sure it would warrant a 3.0 since it’s similar in feel to 2.40. 3.0 would probably entail something totally different. Something like a new look or a new engine
      or something like that. But I do agree with you that stuck updates and platform-end-of-support should’ve been more planned out.

  4. I have had SeaMonkey 2.46 and OSX64 running successfully for some time. Although now I’m experiencing error messages on some sites. Such as Craigslist.org. Images won’t load on some dynamic sites for some odd reason.

Leave a Reply

Your email address will not be published. Required fields are marked *