Depricate renderer2, and and explainer on docs

Description

As Renderer2 is mostly tied to Viewengine, it should be marked as deprecated. Also, there should be a note in the docs explaining why renderer2 is no longer the recommended way to DOM manipulation. This is needed because in the Angular community, there is still this idea that they should use it, and this idea is watched up by time, but most missed the notice.

What is the affected URL?

nvt

Please provide the steps to reproduce the issue

nvt

Please provide the expected behavior vs the actual behavior you encountered

No response

Please provide a screenshot if possible

No response

Please provide the exception or error you saw

No response

Is this a browser-specific issue? If so, please specify the device, browser, and version.

No response

[SanderElias]

@ohois

class SomeComponent {
   doc = inject(DOCUMENT)
   
   ngOninit() {
     const document = this.doc;
     document.createElement('div')
     ... and so on
   }
}

So, inject DOCUMENT and use that like the old-fashioned way to do whatever you desire.

[edusperoni]

Although I understand the reasoning behind it, the renderer interface might still be useful do use internally especially due to some extra optional APIs that can be used. One example is destroyNode, which is not in the dom spec but is useful for some clean ups on custom renderer implementations.

https://github.com/angular/angular/blob/6a88bad0192516f26a5a008c0634b73456b9447c/packages/core/src/render3/node_manipulation.ts#L95

Internally it seems to also be used for animations, where we need to intercept the node removal and sometimes delay the actual removal to a later time, which would be a bit troublesome to do if we had to override DOCUMENT with custom implementations of the methods needed:

https://github.com/angular/angular/blob/39b72e208b46d80f1d9a802cebf043c2ccf3c5f2/packages/platform-browser/animations/src/animation_renderer.ts#L22

https://github.com/angular/angular/blob/39b72e208b46d80f1d9a802cebf043c2ccf3c5f2/packages/platform-browser/animations/src/animation_renderer.ts#L176-L178

So maybe it having it moved to an internal API would make more sense? Then again, I’m not sure the implications would be if people are using Renderer2 specifically to trigger animations.