3 ms·
Good points. A couple of comments: > I wanted Strongtalk, and they gave us Ocaml Pithy, and there's some truth to that, but I would point out that (a) Strong
by mpweiher 10y ago
Good points. A couple of comments:
> I wanted Strongtalk, and they gave us Ocaml
Pithy, and there's some truth to that, but I would point out that (a) StrongTalk is now well over 20 years old (b) it has a sophisticated type-system that could certainly have been developed further and (c) it requires a JIT for performance.
But "Objective-C without the C" does point very strongly in the direction of Smalltalk, and a Smalltalk language that can be AOT compiled roughly as efficiently as Objective-C and is at least as compatible with C/Objective-C seems like not too much of a challenge.
After all, Objective-C now has tagged pointer objects, so a lot of the need for primitive objects has gone away. So let all literals/variables be objects by default and the syntactic overhead due to duplication goes away ( 1, @1, "string, @"nsstring" ).
What if we want "C" level primitives? Just type them:
| aNumber |
| <NSNumber> aNumber |
| <int> aCInteger |
Pointers are tricker and should, IMHO, be generalized to 1st class references that subsume things like KVC/KVO/bindings, file references, URIs etc. (see http://objective.st/URIs http://objective.st/URIs ).
So the point is not 'Objective-C forever', but rather: let's actually learn from what was good and bad about Objective-C and base our language design on that, rather than coming completely from left field and then only putting in compatibility kludges.
Then you wouldn't have the situation that we have now where people are clamoring for "pure Swift" versions of...well pretty much everything, and those things are, if "pure Swift" going to incompatible with what is there now. And more importantly, not build on the knowledge/learnings of what is arguably the best UI framework ever built.