Indeed, nor the world nor freedom of information will die here, but that doesn't mean it's a step forward.
Indeed, nor the world nor freedom of information will die here, but that doesn't mean it's a step forward.
Is it? I've never once used Slack. It's not on any of my devices. But email is and it works great.
We use our personal emails to set up the accounts. It's an interesting experiment that seems to be working fine so far. Not sure how it will work as we continue to grow (only about 40 employees right now.)
I would object to that. Personal and business don't mix.
I don't know about this one. For example, I'm not going to invite every one of our clients to our Slack as a single-channel guest, nor am I going to be joining their Slack workspaces (if any of them even have one - most of them are in the Microsoft ecosystem). I'm also not going to do that with every vendor I'm in contact with, and so on — email is much more convenient. That being said, most of our internal communication within the company is on Slack, but that's a small slice of what emails are used for.
The main difference is that Slack lacks a unique global id, so you can't add a user in Figma based on it's Slack ID unless you have a Figma / Slack integration. Email still rules for these use-cases - which is exactly why open-standards (such as email, RSS, etc.) are better than proprietary APIs that repeat the same use-cases over and over.
I'm by no means a MS fanboy but I find your comment odd...
How are they doing this exactly? I'm genuinely curious where you're coming from...
Teams is bundled into O365 but you can use Slack, Mattermost or whatever other product you want.
Then why should they spend another $100-300/year/user for a tool that on paper does what things like Slack does.
I'd expect zoom to go the same way in the next 12-18 months too.