It is also big news to folks who write a lot of templates, because something like this allows them to create a toolchain which spits out WP templates, as opposed to having to e.g. having a template framework that templates are built against. This means that they can do across-the-board updates much more easily. That's a huge win if, for example, you're a company that publishes 100+ templates and somebody reports an XSS vulnerability in a commonly repeated component of one of them. (I don't know if their other 99 templates are patched yet so I won't go pointing fingers, but suffice it to say this happened.)
+ Kidding, kidding. OK, mostly kidding.
Still, I dislike how the programming community jumps on someone for making something interesting— even if it's not immediately useful for everyone. I get the same feeling in reddit's /r/programming whenever a post pops up about someone using a "NoSQL" database. It seems the majority of comments tend to be people negatively criticizing the OP's choice instead of providing something constructive to the existing project.
until you are victim of a reddit-effect and your precious site goes down. or some yet another security hole is published and taken advantage of by thousands of spammers. I got nothing against wordpress and it's community, but AFAIR (nowadays I don't touch it) the wordpress ecosystem was full of unsecure plugins with awful performance, written by unqualified programmers.