[TurboHaskal]

Can you elaborate why is it a better fit?

Have you evaluated CAPI? Have you looked into building Cocoa applications with Clozure CL?

[mark_l_watson]

CAPI is great, very well designed and implemented.

The advantage of Swift and SwiftUI is that my application can run on both a MacBook and iPad, sync data with iCloud.

The advantage of LispWorks is that I could fairly easily support both Mac and Windows (and Linux).

I spent two evenings last week playing with Clozure CL and its Cocoa support. It has low level APIs and I had a peculiar issue with sometimes not being enter text into input components.

EDIT: to be clear, in general I love Clozure CL. In this instance I was probably shooting myself in the foot, somehow, or maybe the issue was that I blew the install in some way getting it running on Catalina which took over an hour. The Catalina problems are hopefully just short term issues.

[fiddlerwoaroof]

I haven’t used it myself, but EQL5 is attempting to make it possible to use ECL to iOS and Android apps

[TurboHaskal]

LispWorks also has offers an iOS/Android runtime, but no CAPI unfortunately.

[mark_l_watson]

The iOS runtime product allows you to write native libraries, but not do UI directly.

CAPI supports at least Mac, Windows, and Linux.

BTW, it just took me about 40 minutes using CAPI to reproduce what took a couple of hours this morning doing the same UI in Swift and SwiftUI.

[fiddlerwoaroof]

Yeah, EQL5 can be used for UIs, if I understand correctly because it builds on ECL to compile CL to C