3 ms·

You call me a shill and then say you’d switch to IRC over teams. IRC has no features compared to teams - screen sharing, voice/video, threaded discussion, calen

You call me a shill and then say you’d switch to IRC over teams. IRC has no features compared to teams - screen sharing, voice/video, threaded discussion, calendars, a mobile client with all these features, etc.. This implies you don’t really care about capability at all. You have some beef with Microsoft where you’d rather have nothing than something to avoid using a product you have a irrational bias against.

laumars 5y ago
> You call me a shill No, I said you were shilling. I don’t think you’re a shill but your posts are definitely shilling the product > and then say you’d switch to IRC over teams. For text chat. Yes. I also said that was an extreme case however IRC is still more intuitive than Teams for text chat. > IRC has no features compared to teams - screen sharing, voice/video, threaded discussion, calendars, a mobile client with all these features, etc.. Have you even read a single bloody thing I’ve posted? How many times have I said I don’t give a crap about mobile support because 99% of my usage is on a laptop? How many times have I said that Teams suffers from having too many features rather than doing one thing well. It’s like talking to a brick wall… Also I did say IRC specifically for text chat. > This implies you don’t really care about capability at all You’re conflating comparability with feature bloat. I’m all for comparability as long as it doesn’t harm usability. But comparability can be in the form of supporting 3rd party API hooks - it doesn’t have to mean bundling every feature into a confused user interface. This is where the UNIX philosophy comes in: everything in UNIX is compatible with each other but each individual program is designed to do only one thing and do it well. Now I’m not saying we should have separate video conferencing, calendars, text chat, etc. However in the case of Teams it suffers from trying to do everything. It’s the “Jack of all trades, master if none”. So naturally I will use a program that specialises in a specific area well if it improves my productivity. For me using a better text chat solution improves my and my teams productivity vs using MS Teams for everything. > You have some beef with Microsoft where you’d rather have nothing than something to avoid using a product you have a irrational bias against. Enough with the name calling. There’s no need. Especially when the issue here is your own reading comprehension. I’ve given clear reasons why I don’t like Teams. You obviously disagree, which is fine. But at least read my comments before replying with your ridiculous bullshit. “Ridiculous” because you’re consistently citing examples of stuff I’ve already discussed as not a requirement in literally the previous post. Which you’d know if you’d bothered to read my entire posts properly.

laumars 5y ago

> You call me a shill No, I said you were shilling. I don’t think you’re a shill but your posts are definitely shilling the product > and then say you’d switch to IRC over teams. For text chat. Yes. I also said that was an extreme case however IRC is still more intuitive than Teams for text chat. > IRC has no features compared to teams - screen sharing, voice/video, threaded discussion, calendars, a mobile client with all these features, etc.. Have you even read a single bloody thing I’ve posted? How many times have I said I don’t give a crap about mobile support because 99% of my usage is on a laptop? How many times have I said that Teams suffers from having too many features rather than doing one thing well. It’s like talking to a brick wall… Also I did say IRC specifically for text chat. > This implies you don’t really care about capability at all You’re conflating comparability with feature bloat. I’m all for comparability as long as it doesn’t harm usability. But comparability can be in the form of supporting 3rd party API hooks - it doesn’t have to mean bundling every feature into a confused user interface. This is where the UNIX philosophy comes in: everything in UNIX is compatible with each other but each individual program is designed to do only one thing and do it well. Now I’m not saying we should have separate video conferencing, calendars, text chat, etc. However in the case of Teams it suffers from trying to do everything. It’s the “Jack of all trades, master if none”. So naturally I will use a program that specialises in a specific area well if it improves my productivity. For me using a better text chat solution improves my and my teams productivity vs using MS Teams for everything. > You have some beef with Microsoft where you’d rather have nothing than something to avoid using a product you have a irrational bias against. Enough with the name calling. There’s no need. Especially when the issue here is your own reading comprehension. I’ve given clear reasons why I don’t like Teams. You obviously disagree, which is fine. But at least read my comments before replying with your ridiculous bullshit. “Ridiculous” because you’re consistently citing examples of stuff I’ve already discussed as not a requirement in literally the previous post. Which you’d know if you’d bothered to read my entire posts properly.