> [0] https://news.ycombinator.com/item?id=38395603 https://news.ycombinator.com/item?id=38395603 In that post, I was just drawing a parallel to try and compar

> [0] https://news.ycombinator.com/item?id=38395603 https://news.ycombinator.com/item?id=38395603 In that post, I was just drawing a parallel to try and compare QML with some other better known technology. My point was not to say that it is actually HTML that goes into the program. I'm sorry if it caused confusion. My message was meant as a bird's eye technology comparison, ignoring the fine details. A different, more to the point take is: just like a web browser reads HTML and ends up interpreting a visual representation of a page, the QML engine will read a QML file and end up with a hardware-accelerated visualization of it. Qt just gives you the tools for that. If you don't need a hardware-accelerated rendering of a UI, working smoothly at 60fps in consumer devices, then probably QML wouldn't bring much to the table anyway.