Aren't you fearing of infringing Apple's IP since you have reimplemented their API, or you haven't reverse engineered their API (incl. private & internal) so it is actually a clean room design?

I would be very afraid if Apple had been acquired by Sun in the 1990s, for what should be obvious reasons.

But Apple has demonstrated zero interest even in going after ROM bootlegging — I don't expect them to build a case against API reimplementation.

Fixed Links:

https://github.com/jjuran

https://twitter.com/joshuajuran/status/1087557797200433153

Man, that brings back memories, my first Mac was a IIsi running on a b/w monitor. Thanks for your efforts, you are doing really cool projects.

any plans to remove the carbon dependencies?

Short answer: Yes.

Long answer: Advanced Mac Substitute is factored into back end (the emulator itself) and front end (graphics and user input terminal). Writing a new front end from scratch is actually not that much work, and the OS X front end is due for a full rewrite anyway.

This would be an excellent opportunity to contribute that doesn't require any 68K or classic Mac knowledge.

I'd like to, but I'm missing Obj-C/Cocoa knowledge too. ;-)

But I dropped a link with a friend of mine who is super into classic mac, and mac in general.

The secret is to bang the rocks together. ;-)

In the meantime, you could run the Linux framebuffer front end, which, strictly speaking, doesn't have Carbon dependencies. :-D

I dont have a machine that I can run Linux Framebuffer on, I'd be better of building it on my G4, to asking a friend to compile it for me, so I can run it under mojave

In that case, 10.4 and 10.5 are options. There's also a front end that works in classic Mac OS, which a G4 is fast enough to run usably. It's not in the HOWTO yet, but I can add it.