I'm used to the software industry being isolated (vice versa) from the games industry, but I'm a bit surprised by this point because "streaming text" is a pattern inherent to video games running on low powered computers (i.e. 8/16 bit game consoles) and games continue to implement this as a stylistic (or aesthetic) choice today.
Then, thinking about it for more than a second:
Text streaming into view is also inherent to [slow] "network" connections, including the early internet and terminal interfaces (paper and CRT), the default way that computer text appeared for decades. These are less common, though still present today, but a keen-eyed observer [and I genuinely place Nielsen in this category] will surely have noticed the film & TV industry is still running with the trope/meme of text-appears-slowly as the best way to show computer action.
A more relevant example for a huge number of people is found on Tik Tok videos, where it's the default way for text to appear on screen[0]. Platforms desperately chasing Tik Tok have adopted the same effect -- it's a significant part of the aesthetic -- even Youtube's autogenerated captions[1][2][3] on "normal" videos.
[0] I mean "default" aesthetically, purely looking at the output. Not a "default" option like a software thing.
[1] which now come on by default if you have actual captions enabled -- it used to be like a separate language choice, like how if you select Italian subtitles it won't give you Spanish -- Valve^wYougle please fix.
[2] And these are arguably not really captions, by the way. Ignoring how wrong they are, and other issues, I'm just talking about in relation to the subject of this comment: captions and subtitles don't appear one word at a time. Show me a reasonably long phrase and let me read it. The / one / word / at / a / [music] / time / thing / is / a hippo / not / it / and / I / don't / receive / true / meaning. ('hypnotic', by the way)
[3] Yes, this is presumably AI. No, I don't think that undermines my point. It's still a choice (the people in charge did the choosing, not the confabulator), and it's a choice that goes against the extremely well established best practices for captioning as an accessibility service, as I whinged above[2].