I'm not affiliated with Tower except as a satisfied user. Come to think of it, I'm going to suggest we change our process.) (In my defense, the process established at work requires a deploy of a tag to STG once every 2 weeks, but the tag must be deployed to STG every week, leading to a situation where the STG tag must be deleted and recreated. Not sure if it's Github or Tower, but deleting those items and then recreating them often yields an error that the item still exists. The only trouble I've experienced is deleting branches and tags from Github. To rename the repo root directory, one should copy the origin root directory naming it to the new name and then run Renaming repos is straightforward but doing so does not rename the directory in the filesystem. I frequently pick through dozens of lines of code for a granular commit history, sometimes backing up a commit, saving a commit as a patch, (then) amending some lines to a previous commit, staging/unstaging non-consecutive additions and deletions, etc. This is different than my experience of Tower and Tower 2. Slack exists now because they built the stuff that Hipchat didn't. It's not that Hipchat could have potentially competed with Slack it's that Hipchat could have easily crushed Slack. Slack launched into an opening that Hipchat created by stagnating. Back in 2013 the Hipchat/Slack race was still pretty close, and that's after Hipchat had spent the last year doing nothing. Further, when Slack launched, it wasn't nearly as good as it is now: They've made significant improvements over the years. (Slack launched August 2013 Hipchat purchased March 2012.) And back in 2012 Hipchat was almost exactly what it is today: A functional chat app with searchable logs, native clients for many platforms, a somewhat clunky UI, and some persistent issues with syncing and reliability. Hipchat was purchased by Atlassian before Slack even launched. We can debate counterfactuals all day, but the potential was absolutely there. If Hipchat was not bought by Atlassian, it will be a serious contender for Slack?
0 Comments
Leave a Reply. |