Integration about aurelia HOT 5 CLOSED

I think AOT can play a role, but it might be easier if it can be based on a known abstraction pattern. For example DOM.appendChild(parent, child) can be implemented to actually work at runtime without any AOT, but it's also possible to have an AOT process convert this into parent.appendChild(child) with 100% accuracy. It could also be converted to any other API such as parent.add(child) or child.appendTo(parent) or whatever the target API supports. But having the DOM APIs as known, distinguishable operations, enables us to get it working today without any AOT and later, reliably build an AOT mechanism to produce slightly more optimized code.

from aurelia.

You think AOT could play a role here? Replace HTML-specific api calls with the appropriate compatible other UI api calls? Or maybe have separate plugin packages instead and try to keep templating free of HTML as much as possible?

from aurelia.

Agree, the DOM api is actually a great marker api for the AOT to optimize. Note to self: use it more :)

from aurelia.

Things have changed a bit, but do you all think we can close this now that we've factored things out to separate rendering?

from aurelia.

Yes. Its good for now

from aurelia.