5 ms·
Keep in mind that Ripcord only needs to implement support for whatever Slack has already decided to implement. They don't need to do the whole "iterative design
by joepie91_ 7y ago
Keep in mind that Ripcord only needs to implement support for whatever Slack has already decided to implement. They don't need to do the whole "iterative design" process (which Slack is doing for them), which is precisely the part where C++/Qt things tend to fare poorly.
- TeMPOraL 7y agoThat doesn't explain why Slack seemingly can't do it. They could literally hire the Ripcord author and pay him to continue development, and sell Ripcord as Slack Lite. It would be peanuts for them, and it would vastly improve their product offering.
- zentiggr 7y agoBut then it wouldn't be theirs, and that's clearly more important than success now.
- malvosenior 7y agoSlack should stop iterating as each time they do it the product gets worse. They're not good at this.