If you have better ideas / solutions, I'm sure people will listen. I can provide you with an experience for a (any future) production from start to finish that you can observe.
Sometimes it's the companies that dictate standards. FD is notorious slow mover, yet it's 'an industry standard. I worked on one script with another writer. At that stage it was only two of us drafting the idea and I had a need to see what has changed in a script since I sent him my last version and vice versa. I mailed the dev of Fade In if he could just include a diff (yes, our beloved diff) somehow inside of Fade In. A day or two later it was in. I use it now constantly. Same ol' diff we're used to, kind of looks same as on github as well. Red and green lines and all.
This is an industry with lots of resources and a keen eye on new technologies. If you come up with something that optimises anything in workflow, it will come to open hands.
If the industry is open for suggestions, then I have a question: how can one make people who design futuristic displays and hacking scenes stop including webpage source as scrolling code examples? Freeze-framing a scene to see HTML+jQuery must be well on its way to become a Hollywood trope at this point! Maybe a library of categorized, MIT-licensed (or something) code samples would be of help? E.g. these snippets look like hacking, these look like future robot AI code, etc.
This is actually a really good idea, but it will require industry to step in and provide it. The number of films and shows that get it right are almost nil, but there aren't any consequences when they screw it up. The phone companies stepped in with 555 numbers when they got complaints from customers about people dialing numbers that appeared in films. But with no consequence for showing crappy or nonsensical code, either the writers/video playback guys are going to have to get better (this will happen with increased technical literacy over time, but will be pushed by increased audience technical literacy), or (the software) industry is going to have to step in with its own solutions.
If you want to make it happen right away, make a royalty free stock footage archive in 4k of various snippets of code with metadata on what it's for. Less work=more adoption.
Sometimes it's the companies that dictate standards. FD is notorious slow mover, yet it's 'an industry standard. I worked on one script with another writer. At that stage it was only two of us drafting the idea and I had a need to see what has changed in a script since I sent him my last version and vice versa. I mailed the dev of Fade In if he could just include a diff (yes, our beloved diff) somehow inside of Fade In. A day or two later it was in. I use it now constantly. Same ol' diff we're used to, kind of looks same as on github as well. Red and green lines and all.
This is an industry with lots of resources and a keen eye on new technologies. If you come up with something that optimises anything in workflow, it will come to open hands.