And it's not only on the development end. It's also when you're educating and training. With Zen, it was all about ObjectScript and defining a class, plus a little javascript here and there. You didn't have to devote extra training and learning to the second system.
Rich, I understand all of that. Why, though, do answers to those of us who like Zen always including language like:
". . . could never hope to reach feature parity with more broadly accepted frame works like Angular and the others listed above . . ."
". . . that could never achieve feature parity with those mass market offerings . . ."
I know I'm newer than a lot of people here, but I have yet to see anyone asking about Zen asking for feature parity with any of those other front ends. Meanwhile, the part that actually matters gets discounted:
". . . could only beat them in providing faster, more efficient access to the data layer."
There doesn't seem to be a very good understanding of why some of us are still as attached to Zen as we are (other than momentum). That fast, efficient access to the data layer is extremely important, and we like being able to handle the front end and back end together, seemlessly writing the code it takes to do whatever we need to do on both at once. Zen also allowed us to do all of this using the same skill set that we used for everything else in our projects instead of having to learn two entirely different things for the front and back.
Absolutely none of this has anything to do with a desire for something Zen-like with all the bells and whistles of something like Angular.
You haven't added your hgroup to your page anywhere. You'll need to figure out what its parent element should be and use the %AddChild method of that Zen component to add the hgroup somewhere, just like you added your maxData to the hgroup.