> over 300,000 rows<p>Any process you ever enable in code will be pushed to limits you never dreamed possible. This is exactly where discoverability can come into play - someone starts by copying 50 rows and using that to get their job done, and may never realize there are other ways (CSV export, etc).<p>If code can "recognize" when something like this is being done and provide documentation on other ways, it can help people learn new methods.
> This is known as clipboard delay-rendering<p>Aha, so that's why Word[1] just explicitly asked me if I want to save the current copied image before quitting. It's probably asking before loading something big into memory?.<p>[1] <a href="https://i.imgur.com/sNfE3Be.png" rel="nofollow">https://i.imgur.com/sNfE3Be.png</a>
Side note/feel good moment: the author Raymond Chen is an OG beyond-super-engineer at Microsoft, and is an incredible person to work with. He assisted me with my intern project many years ago, and was amazingly eager to share his wealth of experience with a green-eared intern from outside his org.<p>Thanks Raymond! I decided to go the startup route instead of returning to MSFT, but you were an inspiration all the same.
The Windows Clipboard, for all of its problems, remains one of the easiest program-to-program communication methods to use in modern GUIs.<p>I can take a screenshot of my Firefox with "PrtScn" button (moving a bitmap of the page into the Clipboard), paste it into Microsoft Paint, edit it a bit, and then copy/paste that into my Discord chat screen for commentary.<p>--------<p>Yes, Linux / *Nix users have pipes and great text processing tools. Yes, Powershell has interesting objects that can be passed round. But practically speaking? Most of my "inter-process communications" is over this silly "Clipboard" Windows has, and it works way better than it probably should.
Raymond's blog always hits a note of morbid fascination. At times it almost feels like schadenfreude.
"Neat, but thank God I didn't have to be the one that wrote/discovered that."
The Old New Thing and Dave's Garage (on youtube) have helped me develop an appreciation for the decisions made in Windows development, kinda wish we had this kind of stuff from the Mac and Linux side of things.
Follow up post: "How can I wait more than 30 seconds for a delay-rendered clipboard format to become rendered?"<p><a href="https://devblogs.microsoft.com/oldnewthing/20220609-00/?p=106731" rel="nofollow">https://devblogs.microsoft.com/oldnewthing/20220609-00/?p=10...</a>
> Next time, we’ll see what we can do to extend this timeout.<p>That, somehow, seems like the wrong conclusion. Why not try to solve the problem of Excel taking longer than 30 seconds to export a RTF table?
I'm actually quite surprised that it takes <i>over 30 seconds</i> to go through only 300000 items and generate some text with them. Unless the story is from ancient times, that is.