Having said that, there's also 'reply to thread and also share to channel', making it even worse. I think that one's the closest Slack has to fixing threading's problems though - if you're aware of it being a potential issue, you can at least highlight it.
It'd be good if there were an 'active thread(s)' thing that appeared on the right side or something (at the bottom of what is the the thread panel when one's open, I'm imagining though. Easy to ignore, but when you're checking if there's new messages in your main channel you'd also see if there were new thread activity.
Quite simply: you don't know what you are missing.
I was sceptical at first as well, but having the ability to branch off into separate sub-topics while still maintaining easy visibility is extremely nice for organizing conversations and catching up on things you missed in busy channels.
The nice thing is: you can just use flat channels where appropriate, or just ignore the nested topics and read a channel as a regular continuous stream.
It's incredibly conducive to long-form discussions and organizing information, while still retaining the casualness of a chat when required.
TL;DR Slack threads are an after-thought add-on, Zulips topics are a first-class citizen.
Slacks threads can branch of at any point from any message in a channel - if you miss the start of the thread message, it disappears unless someone cross-posts to the channel or mentions you. This is by far the biggest problem I have with slack threads.
Zulip organizes into streams and topics, streams being roughly equivalent to channels and topics similar to threads. However, unlike slack, every message must live in a topic. Topics that have seen a message lately bubble to the top, topics that don't see activity fall to the bottom. You can still see the full stream in chronological order, but messages are grouped by and visibly marked with the topic they belong to. This makes it much easier to both follow a stream and still mentally follow multiple conversations in the same stream.
It's half-baked, but it seems like a great alternative to regular presentation: linear history, but filterable.
Discord also does not have threads. I've heard some complaints about it, but not many.
Threads in Zulip seem to change it into a different kind of app. I don't see how the Slack workspaces that I've used heavily would work with it. There are about 15 channels in my sidebar. Making them nested would turn it into 75, assuming 5 threads per channel. Perhaps there wouldn't need to be as many top-level channels with Zulip threads, but it makes it into a whole different paradigm. They are also missing Slack-style threads. I don't think it would be good to adopt it.