Earlier quoted context omitted.
I've also noticed that in a lot of tech-related social circles people are increasingly choosing Discord over Slack. That's a trend I totally didn't expect: at least until a few years ago it was clear that Discord was for gamers and Slack was for work and everyone else. That changed quickly. Impressive indeed!
Slack uses a language that is like markdown, but is not markdown, which is annoying for engineers. Slack does not support syntax highlighting of code blocks. Discord uses proper markdown and supports syntax highlighting. These are two things that make me think Discord is better specifically for engineers, aside from it just being generally way better.
It does, but only if you make your code block into its own post as a "text snippet." (I assume this is because Slack's internal markup doesn't allow regions to have parameterized metadata, but there is parameterized metadata at the chat-post-event level.)
You also get other benefits of doing this, e.g. being able to collapse the snippet, download it, etc. Code pasted into Slack should really always be pasted as a snippet. I just wish it auto-detected you were trying to do that and offered to make a snippet.