For instance, I enjoyed being a janitor for my Arch Linux install for a while - it taught me a lot - but eventually I switched to MacOS because I actually wanted to ignore my OS and focus on the code I was writing and connecting to WiFi reliably.
If you are putting your time into something, it makes some sense for it to be something you value.
I feel this. I was a distro-hopper for years. I eventually settled on just using Ubuntu LTS for ease but definitely benefited from the time I spent nurturing my arch laptop.
However, still very annoying having to rearrange meetings because you did an upgrade and some X11 config needed to change and so you can't even boot a GUI for a bit.
Bell happened to be one of those companies. You could walk into another door in Bell (or AT&T) and drive to a room much less tolerant of swimming against the stream.
Both the good outcomes and the bad outcomes. Cue the recent Slack WYSIWYG editor woes.
Slack used to have an IRC gateway, allowing anybody to peruse it from any OS, on any device, with any UX. The Slack corp. chose to supply UI for one popular platform (Electron), and cut off[1] any other means of access. This single platform focus did put Slack in full control of the UI and UX of the messenger, and able to force the WYSIWYG editor on all users.
Without the overwhelming dominance of one platform (Electron), Slack most probably would feel the need to maintain the fully featured IRC gateway, letting people interface with it fully via alternative means.
--
[1] the APIs are un(der?)documented, changing, and you are on your own
1. Is it FOSS?
2. Can I use it in Weechat?
That's really all that matters to me. I currently use Weechat to handle IRC and Matrix.org.
I've had to use Slack in an internship in the past. Thanks for mentioning wee-slack; I'll keep an eye on it should I be subjected to a proprietary IM service again.
I can see people giving in just to get rid of that kind of continuous low key harassment.
That's not to say that you need everyone to be a mindless drone, but just like reinforcement learning works best with a healthy balance (usually like 90/10) of exploitation and exploration, society works best when a few people explore new options and the majority follows the emergent consensus.
Per most of the reading I've done on "Why software development time planning is so difficult", the problem lies with bounding uncertainty.
We're pretty good at estimating business as usual, but much less so at producing a number when "there are 3 items, each of which has a ~10% chance of adding 10x happy path time" holds. Or even identifying it might hold!
That someone has already found a way to thread the minefield, or dealt with any unavoidable mines, is valuable.