Thread:Talk:Requests for comment/HTML templating library/KnockoutProposal/General thoughts/reply (2)

Some replies:
 * 1) Possibly, although I'd imagine it to be possible to check in a pre-minified version if we want.
 * 2) For client-side rendering the main task is hooking up messages etc. We can also syntactically restrict what is allowed in expressions (for sanity and compatibility with server-side templates), but that is really optional. Stock KnockoutJS can be used as-is (and is already used by analytics), although I agree that RL integration is very desirable for MW.
 * 3) Basically see 2), either by convention or by enforcing it in the KnockoutJS expression compiler (a simple regexp).
 * 4) I think we touched on this in the discussion. We can basically compile messages to the JSON IR and then execute it using the same runtime.
 * 5) KnockoutJS templates can be dynamically added in the model (as a reference to a DOM node) or as an id in the page DOM. The details of the RL integration are not yet set in stone. We will definitely look closely at what has been done in that area so far (thanks for the links!) and will solicit input.
 * 6) We actually thought about data sources a bit, with the option to pull data asynchronously vs. statically determining the data that is going to be needed at compile time and pre-loading it. The problem with statically determining data sources is that you need to be conservative about which branches are taken, so you might end up more data than actually needed. On the server we'll probably do this as an async / parallel pull similar to the way Parsoid works internally. On the client the expense depends on whether the content is pre-rendered (and only needs to be updated later) or not.