3 ms·

JIT for declarative markup? Has that even been done before?

• rubber_duck 10y ago
  QML is basically a JavaScript superset ?
  • once-in-a-while 10y ago
    Yeah, it's that bad... If all of your code base is C++, what do you think the mindset is of the main developers? The only compromise they were able to allow themselves to think in was... ECMAScript. Sad.
    • sirtaj 10y ago
      Indeed, what kind of fool picks a UI scripting language most likely to already be used by the vast majority of interface designers.
• CarVac 10y ago
  QML has always had it, as far as I know. It makes for a little pause when loading an application as the logic is compiled. I'm not sure what other markup languages have done this, though. They do have a Qt Quick compiler though which removes the need to JIT the user interface; maybe next release it'll see the light of day on the open-source side of things.
  • distances 10y ago
    As far as I understand it's a bit different trade-off: pre-compiled code with no JIT means faster startup, but a bit reduced performance.
• _pmf_ 10y ago
  XAML/BAML/WPF?
  • ygra 10y ago
    But that's AOT compilation of XAML into BAML, with just a parser on the runtime side that creates the object graph. There's no JIT involved, as far as I know.
    • _pmf_ 10y ago
      You're right; I somehow assumed BAML would contain CIL, but instead it's as you said.