3 ms·

This isn't about sending 300 lines of code in a screenshot or something. This is about, "hey, look at these 6 lines which is where I think the problem might be

This isn't about sending 300 lines of code in a screenshot or something. This is about, "hey, look at these 6 lines which is where I think the problem might be". It's not for pasting in a separate editor, why would you do that? It's about providing quick context even if you're on your phone. If you want to go inspect that spot in the file once you're back at your computer then go do that. The screenshot is to save you time because often you can answer just based on it.

CGamesPlay 1y ago
On my phone is a great example of why I don't want your screenshot of a desktop-wide code editor.
- crazygringo 1y ago
  On my phone is exactly when I do want it, because that's where text linewraps and jumbles and becomes totally unreadable. You understand you can just screenshot the code part that is 80 characters wide? You don't have to screenshot the entire full-screen window? But even if someone does include extra width, it takes me about a tenth of a second to pinch-zoom. Which is way quicker than trying to decipher line-wrapped spaghetti.
  - bigstrat2003 1y ago
    > But even if someone does include extra width, it takes me about a tenth of a second to pinch-zoom. Which is way quicker than trying to decipher line-wrapped spaghetti. Strong disagree there. It's far easier to read the line wrapped code than to pinch to zoom. I think you have your answer: you have different preferences than others do, and no amount of explaining is going to make their "I like cats" make sense to your "I like dogs" sensibilities.
    - crazygringo 1y ago
      So you're telling me this is easier to read: +----------------------------- ------------------------------ ---------------------+ | CustomerID | First Name | Last Name | Email | State | Balance | +----------------------------- ------------------------------ ---------------------+ | 000123 | Alice | Ramirez | alice.ramirez@acme.com | NY | 245.50 | | 000124 | Brian | Chen | bchen@northdata.io | CA | 1289.00 | +----------------------------- ------------------------------ ---------------------+ This doesn't seem like a question of different preferences to me. This seems objectively worse. It's not even close.
  - CGamesPlay 1y ago
    > You understand you can just screenshot the code part that is 80 characters wide? You don't have to screenshot the entire full-screen window? Why are you telling me, the recipient of the crappy text screenshot, how to do it better? Line-wrapping is also agitating, I'll give you that. Or worse yet, if the sender doesn't know how to use monospaced fonts in whatever app. I prefer a scrolling text box, which is basically a "pre-pinch-to-zoom'ed" screenshot. But with copy and paste and select. Which is even more useful on the phone, because of its limited symbols, so I can pull the relevant part, modify it, and reply.
    - crazygringo 1y ago
      > I prefer a scrolling text box So do I. But most clients and message mediums don't have support for that. Many don't even have support for monospace at all. Hence, screenshots to get around those limitations.

CGamesPlay 1y ago

On my phone is a great example of why I don't want your screenshot of a desktop-wide code editor.

crazygringo 1y ago
On my phone is exactly when I do want it, because that's where text linewraps and jumbles and becomes totally unreadable. You understand you can just screenshot the code part that is 80 characters wide? You don't have to screenshot the entire full-screen window? But even if someone does include extra width, it takes me about a tenth of a second to pinch-zoom. Which is way quicker than trying to decipher line-wrapped spaghetti.
- bigstrat2003 1y ago
  > But even if someone does include extra width, it takes me about a tenth of a second to pinch-zoom. Which is way quicker than trying to decipher line-wrapped spaghetti. Strong disagree there. It's far easier to read the line wrapped code than to pinch to zoom. I think you have your answer: you have different preferences than others do, and no amount of explaining is going to make their "I like cats" make sense to your "I like dogs" sensibilities.
  - crazygringo 1y ago
    So you're telling me this is easier to read: +----------------------------- ------------------------------ ---------------------+ | CustomerID | First Name | Last Name | Email | State | Balance | +----------------------------- ------------------------------ ---------------------+ | 000123 | Alice | Ramirez | alice.ramirez@acme.com | NY | 245.50 | | 000124 | Brian | Chen | bchen@northdata.io | CA | 1289.00 | +----------------------------- ------------------------------ ---------------------+ This doesn't seem like a question of different preferences to me. This seems objectively worse. It's not even close.
- CGamesPlay 1y ago
  > You understand you can just screenshot the code part that is 80 characters wide? You don't have to screenshot the entire full-screen window? Why are you telling me, the recipient of the crappy text screenshot, how to do it better? Line-wrapping is also agitating, I'll give you that. Or worse yet, if the sender doesn't know how to use monospaced fonts in whatever app. I prefer a scrolling text box, which is basically a "pre-pinch-to-zoom'ed" screenshot. But with copy and paste and select. Which is even more useful on the phone, because of its limited symbols, so I can pull the relevant part, modify it, and reply.
  - crazygringo 1y ago
    > I prefer a scrolling text box So do I. But most clients and message mediums don't have support for that. Many don't even have support for monospace at all. Hence, screenshots to get around those limitations.