Removed WebGLDeferredRenderer.

[mrdoob]

As proposed in #7095. See #18277.

[sunag]

WebGPU should not focus in a DeferredRenderer as default pipeline? This pipeline is used in most high-end games engines like UE4 GTA-V, MGS(Fox Engine)... I understand that WebGL should work on very old devices too, but would we expect this from WebGPU?

[Mugen87]

I would keep forward rendering as the default rendering path for a a WebGPU engine. And probably provide a deferred shading option similar to Unity at a later point.

Comparing three.js to engines like Unreal is not something I would start doing. TBH, even the comparison to Unity is inappropriate. Game engines and lightweight rendering engines are different type of projects and have a totally different target audience and philosophies. For three.js, I don't think deferred shading is a good default.

[sunag]

I didn't want to take the conversation to an engine comparison. Maybe we don't have different projects because we don't have different features. I think Deferred Renderer is a trend just like PBR was. But I believe too we can also think in a WebGPUDeferredRenderer in the future.

[Mugen87]

I guess I would also start with a standalone WebGPUDeferredRenderer and then analyze whether an integration into WebGPURenderer is possible or not. Assuming an integration is doable in a manageable way, deferred shading could then be enabled by defining a new constructor parameter.