Sometimes you want to write something with broken lines and you write in the editor:

That’s right I’m Sokka
It’s pronounced with an Okka
Young Ladies, I rocked ya!

But it ends up looking like this:

That’s right I’m Sokka It’s pronounced with an Okka Young Ladies, I rocked ya!

The fix is to add two spaces between the final character and the carriage return.

I don’t understand what the problem is. CR should be easy enough to translate, and the users intentions are clearly confirmed because they’re looking right at what the expect it to look like when they hit submit.

Why does the user have to add two spaces? Why is the universe like this?

Edit: Holy Shit, look, I’m just an idiot typing text expecting WYSIWYG and I don’t see a good reason for why I’m not getting it other than that programmers lack theory of mind.

  • TootSweet@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    7 days ago

    but why isn’t it “fixed”?

    Because it is useful to many people in certain contexts. It’s not a bug. It truly is a feature. Not something to be “fixed”.

    You may prefer your ice cream strawberry flavored, but that doesn’t mean any ice cream that is instead chocolate flavored is “defective” and needs to be “corrected” or “fixed” to make it strawberry flavored.

    • blackbeans@lemmy.zip
      link
      fedilink
      arrow-up
      1
      ·
      7 days ago

      It can help to give an analogy. But in this case it would be more clear if you would demonstrate the usefulness of this feature by explaining why a user wants to prefer to hit enter and not get any result, instead of hitting enter and getting a newline.

      • TootSweet@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 days ago

        https://lemmyverse.link/lemmy.world/comment/24735359

        Also:

        hit enter and not get any result

        You mean “hit enter and have it not affect the rendered output.” It does produce a result. It makes it appear/act differently in the editor. That’s not “not getting any result.” Just “not getting any result” that’s visible in the rendered output.

        • blackbeans@lemmy.zip
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          6 days ago

          Your explanation is solid but it’s also very dev-centric.
          Wysiwyg has been a solved problem in GUI for over 40 years, when people first started using editors like MacWrite and WordPerfect/Word.

          Web browsers still don’t have a wysiwyg editor built in after decades of development, thereby forcing developers to use js-like solutions. Which obviously suck as you mention.

          So developers resort to a minimalist markup language like markdown (even though html is already a markup language) but then still the implementation is not up to par with what users expect. Most developers aren’t skilled in UX and resort to doing things “the dev way”. That is the explanation why pressing Enter doesn’t always introduce a new line for ordinary users, trying to type a few paragraphs of text on a discussion platform.