4 ms·

Sorry, I really don't see the "bait and switch" here. IRC/XMPP gateways were never a selling point of Slack. Bots were always supposed to use the proprietary We

Sorry, I really don't see the "bait and switch" here. IRC/XMPP gateways were never a selling point of Slack. Bots were always supposed to use the proprietary WebSocket/HTTP APIs, and in all the companies I've worked in that use Slack, not a single person used the IRC or XMPP gateway. Open-source project communities should not be using Slack, if for no reason other than the 10k message limit and the fact that it's annoying to be present in multiple Slacks. I prefer IRC or Gitter for those communities, as they're better designed around the flow of "drop in, drop out" than Slack.

michaelt 9y ago
So I'm a mid-level manager at a company with a few hundred developers. The more developers you hire, the higher the chance you'll start collecting people with obscure (but usually reasonably easy to satisfy) tool preferences. You know, the guy who changes his IDE to emacs key bindings, the guy who does all his e-mail using mutt when everyone else uses gmail, the girl who uses a Dvorak keyboard layout, the guy who insists he works best on a 1024x768 screen, and so on. Having tried a variety of industry tools and thought about about how you work best is usually a good sign[1]. Their favourite tools aren't my favourite tools, but they work for me so if they're not happy, I'm not happy. The bait and switch is we adopted a tool that would keep IRC users happy, and it dropped IRC support. [1] Although I keep my settings conservative, as it's hard for others to pair program or assist you with problems if they can't operate your computer
- warrenm 9y ago
  The beauty of choice is that you and I can have different favorites - so long as we can get our work done, who cares? ____________________ (thanks to http://highscalability.com/blog/2018/3/16/stuff-the-internet-says-on-scalability-for-march-16th-2018.html http://highscalability.com/blog/2018/3/16/stuff-the-internet... for finding this comment)
tjoff 9y ago
The only good thing I've ever heard of Slack is that you can avoid the bloated client and use IRC instead. Probably a great way to reduce friction when introduced.
- FireBeyond 9y ago
  > can could.

michaelt 9y ago

So I'm a mid-level manager at a company with a few hundred developers. The more developers you hire, the higher the chance you'll start collecting people with obscure (but usually reasonably easy to satisfy) tool preferences. You know, the guy who changes his IDE to emacs key bindings, the guy who does all his e-mail using mutt when everyone else uses gmail, the girl who uses a Dvorak keyboard layout, the guy who insists he works best on a 1024x768 screen, and so on. Having tried a variety of industry tools and thought about about how you work best is usually a good sign[1]. Their favourite tools aren't my favourite tools, but they work for me so if they're not happy, I'm not happy. The bait and switch is we adopted a tool that would keep IRC users happy, and it dropped IRC support. [1] Although I keep my settings conservative, as it's hard for others to pair program or assist you with problems if they can't operate your computer

warrenm 9y ago
The beauty of choice is that you and I can have different favorites - so long as we can get our work done, who cares? ____________________ (thanks to http://highscalability.com/blog/2018/3/16/stuff-the-internet-says-on-scalability-for-march-16th-2018.html http://highscalability.com/blog/2018/3/16/stuff-the-internet... for finding this comment)

tjoff 9y ago

The only good thing I've ever heard of Slack is that you can avoid the bloated client and use IRC instead. Probably a great way to reduce friction when introduced.

FireBeyond 9y ago
> can could.