At the component level, one of the challenges for ULS is to be able to have different tradeoffs according to different users.
In this trend, I am looking at context-dependent adaptation via aspects or reflection (where context can include who is the client).
But more generally, supporting tradeoffs in implementations is the objective of open implementations.One of the things I'm also interested in is subjective programming.
So why not subjective open implementations? What could that bring? challenges?
AOP as it is today is not very likely to scale up (what's an application with 100's of aspects?). New forms of modularization should be looked at.
I'm very interested in this perspective. Reflective application right now do not really use their reflective power for producing any part of themselves. What would a genetic software product line look like? and a self-producing line?
Also, reflection abilities are always used a priori: the reflective behavior does not emerge at all. How can we achieve this?
How can we express patterns of stigmergy, ie. driving the emergence of global behavior via local context-related rules?