On 2026-05-06 02:16, Tom Elam wrote:
On 5/5/26 12:08 AM, Alan wrote:
On 2026-05-04 14:33, Tom Elam wrote:
On 5/4/26 4:47 PM, Alan wrote:
Wow. Different applications behave differently.
Very similar Mac App functions with different behavior. I'm not
comparing Final Cut Pro to Adobe products here.
Messaging and email aren't really that similar, Liarboy.
Emails are discrete communications, and while you CAN now thread them
in most email programs, it is an option. That's why most email
conversations include quoted text.
Messages comes out of SMS messaging which has been inherently
threaded conversations for a very long time. Typically one DOESN'T
delete individual messages in thread of messages and replies.
Emails tend to be longer, and one organizes them into folders if
they're worth keeping. Emails are (usually) multiple paragraphs,
meaning that an automatic <Send> on hitting return would be absurd.
Messages are short messages dashed off and nobody is organizing them
into folders. Since they're (often) a single sentence (or even just a
sentence fragment)...
...and because they're delivered immediately, using <Return> as
<Send> works very well. Even if you intended to write more than a
single paragraph...
...(which you CAN do if you learn that <shift-Return> gives you a new
line within a message)...
...the immediacy of the delivery means that the recipient will see
them together anyway.
In short, different use cases result in different interfaces.
But, when you press Return in Mail you get a new line.
Yes, you simpleton. Email has ALWAYS been designed around multiple line text. SMS is designed around SHORT text messages.
Same in every other email app I have ever used.
Duh.
In Messages press Return and you send the message. That's why you need
a Send button in Messages to be consistent with Mail. Both are means
of carrying on a written conversation.
But different KINDS of conversations.
If they were both for the exact same thing, then there would be no point
in having both in the first place, would there?
But lets take a bit of a look around, shall we, simpleton?
WhatsApp is a popular messaging platform...
...and it has no [Send] button. You type a message...
...and hit <return>
How about... ...Telegram?
You type a message...
...and hit <return>; no [Send] button.
What about Snapchat (the web app)?
You guessed it, simpleton: You use <return> to send...
...not a [Send] button.
In the top 5 most popular messaging platforms, there are also "WeChat",
and "Facebook Messenger".
I'm not going to download WeChat to investigate, but I can tell you that Facebook Messenger, in its web interface (they've discontinued the Mac app)...
Say it with me, simpleton!
...it has NO [SEND] BUTTON.
That's right, you hit <return> to send.
On 5/6/26 3:35 PM, Alan wrote:
On 2026-05-06 02:16, Tom Elam wrote:
On 5/5/26 12:08 AM, Alan wrote:
On 2026-05-04 14:33, Tom Elam wrote:
On 5/4/26 4:47 PM, Alan wrote:
Wow. Different applications behave differently.
Very similar Mac App functions with different behavior. I'm not
comparing Final Cut Pro to Adobe products here.
Messaging and email aren't really that similar, Liarboy.
Emails are discrete communications, and while you CAN now thread
them in most email programs, it is an option. That's why most email
conversations include quoted text.
Messages comes out of SMS messaging which has been inherently
threaded conversations for a very long time. Typically one DOESN'T
delete individual messages in thread of messages and replies.
Emails tend to be longer, and one organizes them into folders if
they're worth keeping. Emails are (usually) multiple paragraphs,
meaning that an automatic <Send> on hitting return would be absurd.
Messages are short messages dashed off and nobody is organizing them
into folders. Since they're (often) a single sentence (or even just
a sentence fragment)...
...and because they're delivered immediately, using <Return> as
<Send> works very well. Even if you intended to write more than a
single paragraph...
...(which you CAN do if you learn that <shift-Return> gives you a
new line within a message)...
...the immediacy of the delivery means that the recipient will see
them together anyway.
In short, different use cases result in different interfaces.
But, when you press Return in Mail you get a new line.
Yes, you simpleton. Email has ALWAYS been designed around multiple
line text. SMS is designed around SHORT text messages.
Same in every other email app I have ever used.
Duh.
In Messages press Return and you send the message. That's why you
need a Send button in Messages to be consistent with Mail. Both are
means of carrying on a written conversation.
But different KINDS of conversations.
If they were both for the exact same thing, then there would be no
point in having both in the first place, would there?
But lets take a bit of a look around, shall we, simpleton?
WhatsApp is a popular messaging platform...
...and it has no [Send] button. You type a message...
...and hit <return>
How about... ...Telegram?
You type a message...
...and hit <return>; no [Send] button.
What about Snapchat (the web app)?
You guessed it, simpleton: You use <return> to send...
...not a [Send] button.
In the top 5 most popular messaging platforms, there are also
"WeChat", and "Facebook Messenger".
I'm not going to download WeChat to investigate, but I can tell you
that Facebook Messenger, in its web interface (they've discontinued
the Mac app)...
Say it with me, simpleton!
...it has NO [SEND] BUTTON.
That's right, you hit <return> to send.
All of which are inconsistent with Apple Mail.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,123 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 64:52:38 |
| Calls: | 14,369 |
| Files: | 186,378 |
| D/L today: |
2,147 files (867M bytes) |
| Messages: | 2,539,333 |