This is part of a series of questions which focuses on a project called the Abstraction Project, which aims to abstract the concepts used in language design in the form of a framework.
Another page associated to it related to structural typing can be viewed here. The question related to ease of use can be viewed here.
I have a question associated to the focus of stackoverflow; if someone was interested in writing a language framework and wanted to inquire about possible features, usability and so on.
Since it's not technically a question of 'how to', I wondered whether it would be an appropriate question to post.
The main thing I need assistance with is determining whether something I'm working on is simple enough to use for the Average Joe Programmer. Granted a large portion of this is in the realm of subjectivity; however, there are likely objective views that can be added into this (if most people can't use something, at what point can you objectively record it.) Further related to language features: if something's a bad idea, there can be objective reasons as to why it's a bad idea.
Focus on ease of code synthesis versus explicitly defining the nature of the code (action-based synthesis versus something like CodeDOM which requires explicitly defining the types that describe the actions/code.)
Suggestions, and directions, towards this are appreciated.
