I am along your line, when it comes to the simplicity of use, and the limitations of ASObjC, so we must have something in common.
I am basically thinking of the Foundation framework, and not the AppKit. And I agree to that you may suddenly realize that you have to fork in an Objective-C class here and there, but that shouldn’t be so much of a problem, not here anyway, with the helpful and proficient community of the ASObjC forum.
I meant using ASObjC in the form of cherry picking, use the parts of it that are most convenient for scripts. I may not have found all the cherries yet. And I prefer Objective-C for applications, because I know what I get.
When it comes to libraries, I’ll continue with my script objects until I need to upgrade them. And I’ll never write a dictionary for my own use, as I see from the System Log, that my dictionary wouldn’t be the only one with a problem.
(By the way, I believe totally random four letter codes, conforming to that one must be uppercase to be the best practice for dictionaries, because then a clash is most improbable.)
I have started with organizing my Script Libraries Scripts, with java-package resembling name standard, that I am very happy with.
In the end, ASObjC can do a lot for “pure” AppleScripts, especially when it comes to the foundation framework’s functionality, but not for everything, like sorting, where Nigel has handler I haven’t found yet in Cocoa.
But regex’s without sed/awk seems to be an all good thing, and there are lots of other stuff, like alleviating the need for the Finder/System Events by NSFileManager, which are totally priceless!
I think it is going to take off!