3 ms·
Neat! Was just looking at this last week, currently writing a paper on the problems our current mono-culture is causing, with almost everything being a variant
by mpweiher 9y ago
Neat! Was just looking at this last week, currently writing a paper on the problems our current mono-culture is causing, with almost everything being a variant of the call/return architectural style.
"In evaluating each year’s crop of new programming languages, it is helpful to classify them by the extent to which they permit and encourage the use of effective programming paradigms."
Well, currently the answer to this is very Fordian: you can have any effective paradigm as long as it is call/return. And we will make all other paradigms ineffective, so that works out. :-)
"When we make our paradigms explicit, we find that there are a vast number of them."
And that's the issue: when our languages only support a single paradigm, we then have to encode every other paradigm in such a manner that it becomes implicit in the patterns that are used.
In fact, even OO isn't really supported by current languages: the crux of OO is the connections between the objects, but you generally cannot write down connected objects, you must write procedures that build the connected objects. I've always felt that the people who want to make "object construction" special were on to something, but then completely missed the point.
"Often our programming languages give us no help, or even thwart us, in using even the familiar and low level paradigms."
Hear hear.
Anyway, my take on bringing in language support for appropriate paradigms is setting "paradigm = architectural style", noticing that "architectural style ~= "language metasystem" (start with MOP in OO and generalize), then make all these bits flexible and provide enough syntactic room to make the resulting adaptations as trivially usable as possible.
Yep, it's hard and it's a lot, not least because of this:
"To persuade me of the merit of your language, you must show me how to construct programs in it. I don’t want to discourage the design of new languages; I want to encourage the language designer to become a serious student of the details of the design process."
So there are three levels:
1. Write programs with certain paradigms
2. Create language support for those paradigms
3. Create meta-language support for writing language support for those paradigms.
Slugging away at it:
http://objective.st/ http://objective.st/