Perf: Direct Dom Rendering

Right now, Angular always uses the Renderer to stamp out elements. If we know we run in the browser without web workers, we can do better:

• Generate plain document.createElement / element.setAttribute / element.style.... = ... / element.someProp = ... calls
• Add a flag directDom to CompilerOptions and tsconfig.json to opt into this behavior
• Don’t store allNodes in prod mode any more

Can be implemented with or without #11673. If without: still have a helper function for createElement that automatically adds the right css classes

Add a plugin mechanism to support other kinds of rendering, e.g. for serverside rendering or webworkers or nativescript.

Also support typing the properties in which we store the elements correctly. E.g. with an HTMLDivElement, …

[tbosch]

On by default. Only off in debug mode or when using web workers. On Thu, Nov 3, 2016 at 5:49 PM Suguru Inatomi [e-mail] wrote:

As a result, direct rendering will be an optional feature? or a default behavior?

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/angular/angular/issues/11394#issuecomment-258316762, or mute the thread https://github.com/notifications/unsubscribe-auth/AAqKf80BtH-Z6oKsY4Vj54TcamdCmBedks5q6oExgaJpZM4J2SdZ .

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}