Comment by crazygringo
3 months ago
> people reading can read it
Which is why screenshots help, for the reasons I gave
> people reading can copy and paste it
Why? If there's something like a user ID or error code that the person needs as text, I'll paste that separately. Stuff I include in a screenshot is for understanding, not copying and pasting.
> and people searching can actually find it.
Which is what the message text around the screenshot is for. Which actually includes the relevant keywords, not random tabular data or lines of code which just add noise to search.
> Anybody wanting to look at the actual text in context won't be doing it in the chat, but will rather be opening the file of interest in the appropriate tool, and examining it that way;
Except when they aren't/can't. The whole point of screenshots is for when they can't access something easily that way, which happens for a million different reasons.
> anybody stuck reading the text only in the chat is probably on their phone or something and will be best served by being able to easily see all of it.
Which is what images make far easier to read without being messed up.
> For reading purposes, the question of screen width is best left to the reader. They will have the window set to their preferred width, possibly limited by screen size. If the text has to wrap, so be it.
No it's not. Wrapping destroys indentation and alignment. It's not "so be it", it goes from readable to literally unreadable. I can't change the width of my phone or a lot of viewing areas. I can always scroll an image horizontally though.
> It's better that than having to try to squint at your 3713x211 screen grab on an iPhone (portrait orientation).
Which is why zooming and panning exist. I don't know where you're getting something silly like 3713 pixels though. But if that's the width of some massive table whose layout needs to be preserved, then so be it.
> Which is why zooming and panning exist.
Which loses fidelity in your raster format screenshot world. Alternatively, when text is presented as text, a user can scale it independently for readability. Or as another commenter pointed out, use a screen reader.
You focus on a kind of permissions or network limitation technical access, between the computers in the system, but don't seem to appreciate another very real type of technical access between the user and the leaf computer in the system.
I feel your argument unnecessarily obtuse.
You keep trying to frame that photo is superior, when, sure... The image is superior in your argument only when it's accompanied with text. So is it the image that is important then? No to mention, that is contingent. If that is your point, then, sure, I don't mind, add a screenshot next to the text but, please, give the text.
The main reason the argument doesn't stand up is that some people use screen readers.
Unless you know the person/people you're sending something to can read screenshots, it's only right to at least accompany them with the text.
There's nothing obtuse about it.
You're creating a strawman. Nobody is aruging that you send only a screenshot, devoid of context or explanation or any other text. That's absurd.
The point is, if you need to illustrate code or output then that part gets sent as a screenshot, to preserve readability. It provides extra details and context.
If you want the code or data in text format to dig in, then go get it from the files yourself, because you probably need a broader swath anyways. My message isn't a data repository. I'm including the screenshot so you can understand the issue easily, without having to open anything else.
I'm genuinely mystified by this entire conversation. I'm baffled by this idea of needing to take some example I'm sending in a screenshot and... copy and paste it into a text editor to edit it? Huh? What the heck?
Let me give you some examples that I saw in my professional life and make me angry enough that I am genuinely miffed you can't see this.
Here, check out this hash. Snip! Screenshot! Here, try this code snippet. Screenshot! Here, go to this absurdly long URI. Screenshot! Try configuring your XML this way. Screenshot! (Bonus point for underspecified location)
1 reply →
It's completely obtuse. "I'll include the important bits in a separate text as well, because I already know everything that the other person is going to find important."
Others have made the basically the responses I would make myself, except for 3713 pixels being most of the width of a 4K display, and about the right number of pixels for the interesting part of the error list window in Visual Studio 2022.