I think I see where this went of track and I think this is a grave misunderstanding. "The biggest hurdle in all those systems is understanding what typesetting

I think I see where this went of track and I think this is a grave misunderstanding. "The biggest hurdle in all those systems is understanding what typesetting actually is" Read it as: "The biggest hurdle in all those systems (for the user) is understanding what typesetting actually is" Many programmers approach TeX (and patoline?) as programming environments like programming languages. They are not, even if they allow to build new components (maybe using scripts). I wanted to illustrate the challenges from that perspective. I did not want to fundamentally criticize your ability to tackle those problems or imply that patoline is not fitting to those problems. My biggest problem was that the About page gave me no idea about your system as a typesetting system, only as a programming environment and some of that gives me a bit of a headache. This is by the way shared with many other projects, my pet peeve is a programming language that mentions it's own name only once on the About page and Haskell thrice ;). Be more self-centric! What is patoline, not compared to TeX? If you read anything else out of that - I am sorry for phrasing that wrong. Still, as a maintainer of a software that is often criticized in similar fashions (we build a web framework in Ruby that is not Rails), I would recommend to take the criticism as a less emotional matter. Software is rarely our actual baby and it often helps more to just discuss the actual points of the criticism or check whether there is a misunderstanding (this, in this instance, also applies to me). As a final word: Sorry for what came out of that. I understand your frustration and that you needed to write it off your chest. My reaction was a bit knee-jerk as well.