4 ms·

They had already announced the retirement of Hipchat long before they made their deal with Slack. They agreed to stop development of their Slack competitor name

• dannyw 5y ago
  Stride wasn't really going well. There were some obvious, serious issues with technical and product management, for example the insistence on using Jira's javascript-based textbox rewrite ("Fabric") as the GUI element for composing messages, under the spiel of 'unification'. As "Fabric" is a web component, this meant that mobile apps for Stride essentially had webviews for their input box, introducing additional latency (critical for typing), bugs, inconsistent editing behavior to native iOS/Android UIs, and performance issues especially across lower-spec android devices (it's just a textbox FFS!). Plus, engineers were wasting time figuring out how to sort browser and webview compatibility issues, instead of, you know, implementing a textbox using native technologies which isn't rocket science. To make matters worse, the team working on Fabric was juggling between fixing INPUT BOX bugs on Jira, on Confluence, and on Stride, making it a gigantic mess that kept multiple product managers distracted for the wrong reasons.
  • robertlagrant 5y ago
    Is the input box technology choice really that insurmountable a problem to fix in the future?
  • dbbk 5y ago
    WYSIWYG composers are hard to do well, though. They're certainly not trivial.