Apple was after nothing, they got NeXT in a reverse acquisition, thus Objective-C.
Had they kept their Copland plan, or acquired Be, C++ would be the lucky one.
They only introduced Java in OS X, because initially they were afraid Mac OS community, raised in Object Pascal and C++, weren't that keen into adopting Objective-C.
Once they saw otherwise, Java support was killed, and the Apple specific extensions given to Sun/Oracle.
Sorry but no. Obj-C used to be my bread and butter, I knew it pretty well (alas, poor Yorick! I knew him, Horatio). The only truly dynamic part was message sending and even that got much stricter in later versions of the language, i.e. you wouldn't be able to call any method on any object like before without at least explicitly casting to `id`.
Apple was after “ios and downloadable code for vms/jits that we cannot control is a recipe for disaster” really. And it was.
Partly due to ios “security” based on appstore checks rather than technical ways (private ios apis, calls allowed only under specifically claimed features, and just bugs). Partly due to the fact that running something locally is prone to local vulnerabilities naturally (the same category as “never run curl | bash”).
The only dynamic stuff VM used by Apple is JavaScript.
Even the original lets make HTML5 apps went nowhere, as given the reception, it took less than one year for the official Objective-C SDK to enter the scene, and the whole HTML5 apps idea was thrown away.
It was more of a natural language/DWIM movement, especially from Perl.
(+ one of these days I will turn my "typesafe macro assembler" post-it note into a PoC)