My understanding is that The "Nintendo hired the iNES Developer" story is actually it's own myth!
The person referenced who Nintendo hired is Kawase Tomohiro.
The basis for calling him "The iNES Developer" is that, in a changelog for 0.7 of iNES, Marat Fayzullin - the developer of iNES - wrote: "Sound support completely rewritten, thanks to Kawase Tomohiro"
That is the entirety of the association. That single line in a changelog. Based on similar "thanks" lines it was probably because they reported some emulation issues and not because they personally rewrote the sound support for the emulator, but resulted in Marat doing so. It's actually interesting how these stories seem to change over time. The last time I heard this, the story was that Nintendo had hired somebody who contributed to iNES, which was at least technically true if a bit misleading, but it seems that now the story is that they hired *the* iNES Developer. Which seems particularly silly when we consider the basis is that 8 word changelog line.
My understanding is that TOS and TNG were shot on film and the 1080p versions aren't upscaled but are actually rescanned from the film. TNG supposedly had to basically be re-edited from the original footage after rescanning, but not sure about TOS.
That method wouldn't be possible for DS9 or Voyager as both of those shows were shot digitally at 480p. I remember hearing that there's been some community work that upscales DS9 to 1080p using neural networks, but haven't really been able to find anything concrete about that.
ExtremeTech has a few articles about upscaling DS9 and I think the work has been ongoing for a few years now. Some of the examples are really good but the techniques and technology is changing as the author is working and maybe I'm misremembering but I think the GPU time was measured in months to over a year for the whole series to be upscaled.
When they first started this, a month ago (or so?) I just right-clicked and used block element with uBlock Origin to block the popup and the div element that covered the page to dim it.
I've not seen it since. Only side effect is videos sometimes pause right as they start. I assume because it stops the video and shows the pop up. I can just resume immediately though.
"Clean room" reverse engineering basically has you with two completely separate groups of developers. One group will decompile and analyze the target software, and build a detailed specification of how it works. The second group, with legal, sworn documents that they have never seen even the machine code of the target software - uses those specifications to build the "clone".
A related detail, even things like icon design have gone in a strange direction. In the interest of simplicity they've gone from recognizable to rather amorphous blobs. A button for print has gone from a clearly recognizable image of a printer, enough you could probably even guess the model number, to the icon being a rounded square with another rounded square sticking out the middle top. Many of these newer icons are just too abstract and similar to one another to be recognizable, IMO, and I think the user experience suffers.
My recollection is that the migration tool was really just a tool that would fill your VB6 code with comments telling you that you had to rewrite stuff. Trouble spots were largely related to error handling On Error Goto and error handling blocks had to be refactored into proper Try...Catch blocks, which affected a lot of code, and another trouble spot was all File I/O had to be rewritten/redone, same with any drawing code; Resource files had to be recreated, etc; I don't even think it could load the FRX files but I might be misremembering. I felt it simply wasn't worth even bothering to try to directly convert to VB.NET, and since those programs I wanted to move forward I had to pretty much rewrite anyway, I decided to use C# instead and just make new versions.
The thing that gets me in the originally posted link is that the author decided since this was Air Canada, every single person involved must end their sentences with 'eh'.
The person referenced who Nintendo hired is Kawase Tomohiro.
The basis for calling him "The iNES Developer" is that, in a changelog for 0.7 of iNES, Marat Fayzullin - the developer of iNES - wrote: "Sound support completely rewritten, thanks to Kawase Tomohiro"
That is the entirety of the association. That single line in a changelog. Based on similar "thanks" lines it was probably because they reported some emulation issues and not because they personally rewrote the sound support for the emulator, but resulted in Marat doing so. It's actually interesting how these stories seem to change over time. The last time I heard this, the story was that Nintendo had hired somebody who contributed to iNES, which was at least technically true if a bit misleading, but it seems that now the story is that they hired *the* iNES Developer. Which seems particularly silly when we consider the basis is that 8 word changelog line.