Odds on macOS 10.14 supporting cMP 5,1 ?

[frou]

With 1 month to go, the poll stands at 77% Yes, and 23% No.

Seems overly optimistic to me, but I'll be happy if proved wrong!

 

[flyinmac]

That's how it would be able to differentiate between a 2010 and a 2012. I don't have very much current knowledge about hackintoshing, but afaik a lot of custom settings need to be applied for iCloud services like iMessage to work properly and those settings could not be applied to a Mac Pro using hackintosh tools that are designed for a PC. Apple identifies your Mac by the serial number.

Hackintosh tools set a serial number. And it’s not hard to make a valid number.

And, I have booted a genuine Mac with a Hackintosh configured hard drive. The Mac didn’t complain in the slightest.

 

[Jerry Fritschle]

The one thing we've been told about 10.14 is that it will not run 32-bit apps "without compromise." The first "compromise", that makes sense to me, is to finally stick a fork in Carbon. This has done its job (the transition from the "Classic" Mac OS), and has been deprecated for years. With this in mind, I'm guessing that my 5,1 cheese grater will still be supported, and I'll just have to use an old machine, or boot from another volume with a legacy system, if I can't live without the one Carbon app I still use regularly.

 

[crjackson2134]

I'll make a full disk image before the upgrade. If it breaks things I have to have at the moment, I'll buy another SSD and restore the image. That way I'll have the best of both worlds.

That said, I probably don't own any mission critical apps that aren't x64 already. I likely won't effect me at all personally.

 

[AidenShaw]

The first "compromise", that makes sense to me, is to finally stick a fork in Carbon.

Why does that make sense? Why intentionally break applications?

I regularly use applications built from as far back as early 1995 on my Windows 10 64-bit workstation. Microsoft hasn't intentionally crippled them.

An API is a "contract" between the OS and the developer. Why break contracts?

 

[frou]

Why does that make sense? Why intentionally break applications?

I regularly use applications built from as far back as early 1995 on my Windows 10 64-bit workstation. Microsoft hasn't intentionally crippled them.

An API is a "contract" between the OS and the developer. Why break contracts?

The people who wrote the API have probably retired by now and the current staff would rather not maintain the ancient sh*t

 

[ssgbryan]

The people who wrote the API have probably retired by now and the current staff would rather not maintain the ancient sh*t

Obviously you have never developed software.....

 

[frou]

Obviously you have never developed software.....

Only during university and for a decade after that

 

[flyinmac]

The people who wrote the API have probably retired by now and the current staff would rather not maintain the ancient sh*t

Interesting perspective. We should probably just scrap OS X. It’s based on code older than Apple. We probably should just revert back to Classic versions like OS 8 and OS 9. At least those aren’t relying on underpinnings from the 1960’s like Mac OS 10.x.x. Ok... technically 1969.

iOS should just be scrapped to for relying on the same ancient underpinnings.

Linux should likewise be flogged and sent off in shame.

 

[frou]

Do you guys believe the established concept of deprecation followed by eventual removal is morally wrong or something?

I characterise a dry subject with a bit of human colour and you pitch a fit.

 

[dfred]

http://www.macvidcards.com/blog/osx-mojave-or-4151-just-won-again