With frc it depends a lot more on the specific team and how they work, some teams will very rapidly prototype lots of things to find what works for them, while others will just have an idea they like and start building. It's more of a time management issue than anything.
A very similar thing is also just built in to the screenshot tool, at least in Windows 11, easier for me to use since it's the same keybind as always to take a screenshot, then it's just a tool in it.
GeForce now used to have tons of "issues" with people easily being able to run any app or program they wanted, using a few tricks. Last time I tried it, it seemed like it was all locked down a lot better, but previously it'd still be steam opening the other program.
It was nice while it lasted, since they wanted cyberpunk available day one, it was actually accessible about a week before the game released.
Works very well. I compiled the same c++ code to wasm and native (without optimization), the native version was slower than the wasm one running in this and jit'd, including startup time. Planning on using it for scripting for a game engine I'm slowly working on, instead of being locked into one language.
Another fun thing about steam: There's no setting for the game developer to enable/disable the networking, so if a steam game uses steamworks and doesn't have multiplayer through steam, it can just be modded in and works great.
I've been using this for a while. It lets me have a single simple dev environment that I can access from any machine that I can use a web browser on, which as a student with a school owned laptop, has been very helpful. It gives me a lot more time to work on my projects as long as it doesn't have a gui, which I have to use my personal laptop for only at home. Also useful for managing dev environments for other devs in some settings, so you could give them Chromebooks or similar low power low cost devices. I also set this up for programming for our schools robotics team, works great.