

“AI is the asbestos we are shoveling into the walls of our society and our descendants will be digging it out for generations.”


“AI is the asbestos we are shoveling into the walls of our society and our descendants will be digging it out for generations.”
Hey, now there’s a good idea. Why didn’t I think of that?
May well be more of a Schrödinger’s Douchebag thing, though. 🤷


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.


So, I think I kindof know what you’re getting at here, but you’re not being very precise about it.
First some definitions (just for purposes of this conversation – don’t take this to be any assertion that a particular term always inherently has a particular meaning, it’s just a tool for this conversation specifically):
(As an aside a line break is sometimes accomplished with a “line feed” character. A “carriage return” character is something else that isn’t the same thing. Which is a big part of where the confusion comes from.)
What you’re saying, I think, is that putting a single newline in the source doesn’t result in a line break in the rendered output. Is that right?
In some editors (Vim being one I know of), when plain text word wraps, pressing “down” when the cursor is on the first line of a wrapped series of lines causes the cursor to jump not to the second line of wrapped text, but to the first line after the next newline. To illustrate:
If this line is wrapped due to
being wider than the available
width.
And if this line is on its own line
due to being immediately preceeded
by a newline.
If your cursor in the above example was on the “w” in the first line there, pressing down would take the cursor to the space immediately before “is” in “And if this line is on its own line”.
As a result, it can be quite a pain to deal with word wraps in such editors. This is part of why certain code style guides (like this one and this one have hard limits for how many characters are allowed before the next newline.
Given how much more convenient line breaks can be than word wrapping, people writing source to be rendered into rendered output may wish to be able to insert newlines to cause line breaks in the source without causing any change in the corresponding rendered output.
That all make sense?
At least that’s most likely at least one reason why the people who invented Markdown decided specifically to make Markdown work that way.
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.
I’m glad you’re not in charge. I very much don’t want to go back to the days of having TinyMCE embedded in everything.


I’m not sure why there’s so much confusion.
Because you’re not using the right terminology. ;)


I think they’re talking largely (mostly?) about Markdown. (For instance, in Lemmy, when you stick a newline there, it doesn’t give you a line break in the flow of the text.) And when they say “Carriage Return”, they don’t know what they’re talking about. If I’m interpreting them correctly, I think they just mean “newline”. And when they say “two spaces”, I think they mean two newlines.


Took me longer than I care to admit to figure that out. Heh.



At the heart of every Guild Heighliner, a Navigator floats in a sealed tank of spice gas.


Five bucks says it grows algae too, somehow.
Fallout: Pride Parade
I unpinned this post. See here for context.


I unpinned this post. See here for context.


I unpinned this post. See here for context.


Yeah, I went ahead and did so. Maybe on a forgiveness-rather-than-permission basis. We’ll see what, if anything, comes of it.
I know the feeling. Truly we are living in the strangest timeline.
https://lemmyverse.link/lemmy.world/comment/24735359
Also:
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.