GPU notes

Author: Tyriar

release-notes/images/1_96/editor-gpu.png

@@ -694,9 +694,20 @@ If you notice issues with extension updates, you can disable this functionality
 
 ### Ground work for GPU acceleration in the editor
 
-We are excited to announce that we have started work on enabling GPU acceleration in the editor, [similar to the terminal](https://code.visualstudio.com/docs/terminal/appearance#_gpu-acceleration). The goals of this effort are to reduce input latency and improve scrolling performance.
+We are excited to announce that we have started work on enabling GPU acceleration in the editor, [similar to the terminal](https://code.visualstudio.com/docs/terminal/appearance#_gpu-acceleration). The goals of this effort are to improve the overall coding experience primarily by reducing input latency and improving scrolling performance.
 
-TODO@Tyriar
+This is still early and not ready to test out, but we wanted to share some details about the progress that has been made:
+
+- The GPU renderer is using WebGPU behind the scenes.
+- We're focusing currently on feature parity and correctness over performance.
+- There's a fallback mechanism when GPU acceleration is enabled that allows lines to "fallback" to DOM rendering when it's not fully supported. This means that we can self-host early on and currently incompatible lines will show using the DOM approach instead. Some examples of lines that currently fallback lines over 200 characters, lines with certain monaco decorations (eg. fading unused variables), lines that wrap, and so on.
+- Monaco's inline decorations which allow styling the actual elements containing the charatcers posed a big challenge for this feature as they are styled using CSS. The approach we're using to support most inline decorations without breaking or changing API is to detect the CSS attached to these decorations and then support a subset of common CSS properties, falling back if not all styles are supported.
+
+Here's a screenshot of the feature in action, note the yellow line in the gutter tells us what lines are using fallback rendering. This particular case uses fallback rendering due to the `dontShow` parameter having an inline decoration as it's unused:
+
+![GPU rendering looks mostly the same as DOM rendering currently, a yellow line appears for lines rendered via the DOM](images/1_96/editor-gpu.png)
+
+The issue tracking this work is [#221145](https://github.com/microsoft/vscode/issues/221145) which has frequent updates and more details on progress as it's made.
 
 ## Notable fixes