M2tM wrote:Well, considering every post in here is talking about frameworks, the first question has been asked by every person here.
Every framework I know, and all those mentioned use templates and a templating language. The fact that many use PHP as their templating language may be something that you don't like ... but that does not mean they don't use templates.
M2tM wrote:Functions and classes are "alternative syntax", why not write everything in machine language? What I have here is a layer of abstraction. It is a similar layer of abstraction to other templating languages and in that regard it is an alternative syntax, but it provides more flexibility and has a different focus than other template systems I am aware of and in that regard it is more useful.
I think I addressed this regarding DSLs. Ultimately yours is an alternate syntax. You can defend the rational for your syntax choices all you want. Either people like it or they don't. Whoever uses your system would probably not care about the code as long as everything worked and it was fast. It is the template syntax that is significant. Do you have a complete spec for your YATL?
M2tM wrote:The fact is, I posted this for consideration by peers and I've got more posts talking about unrelated stuff, I count 2 posts directly about the project posted for review (other than my own) and I am responding to the few questions I've found in an attempt to cut through the static. If people don't find it interesting I suppose that's fine, but I was hoping for some honest feedback about the project itself rather than a detailed debate on unrelated frameworks.
I don't think any of it was unrelated. They may be things to did not want to hear ... but that is a different matter. I certainly take into account comments that guys like pytrin and josh post (even if I don't want to hear it

) and have benefited greatly from it.