3 ms·

Yeah this happened at Atlassian, beat for beat. Textbook incompetence. HipChat was a declining dumpster fire with endless outages, so they thought they’d make

by pram 4y ago

Yeah this happened at Atlassian, beat for beat. Textbook incompetence. HipChat was a declining dumpster fire with endless outages, so they thought they’d make a new chat platform from scratch (Stride) So all the development effort was on Stride from that point. It was released, no one used it, and then under a year later it was shitcanned and “sold” to Slack. The dev team was RIF’d. Good shit!

cestith 4y ago
Did a similar thing happen (minus the new product going away) in the Stash to Bitbucket transition? I also wonder how many people are not moving to Bitbucket Cloud when Server and Data Center are discontinued. Gitlab is still available to be self-hosted with full support.
- pram 4y ago
  Stash and Bitbucket “cloud” were completely different codebases. It was kind of a unique case. The HipChat “server” was just a weird fork of the “cloud” version. JIRA and Confluent cloud started off as containerized versions of their on-prem versions. Then they did a big rewrite to make them actually multi-tenant. I haven’t been keeping up but Stash was definitely not the priority at the time.
  - cestith 4y ago
    Bitbucket Cloud wasn't the immediate successor to Stash, though. There have been Bitbucker Server and Bitbucket DC or whatever they're called for years between the retiring of Stash and the retiring of the on-prem solutions. Where I am we already made the transition from Stash to Bitbucket on-prem (not too long after leaving Gitorious for Stash). When our executives heard "cloud VCS", we bought Gitlab licenses and are moving to that. We also left HipChat for Slack shortly after leaving our own OpenFire server for HipChat. We recently left JSM for Zendesk because it apparently is way easier to get quality statistics out of it. We have shadow IT programs all over the company using something other than Jira even though that's the standard the company provides. We're moving from on-prem Confluence to cloud, but there are still many grumbles about it vs something as simple as FOSWiki or MediaWiki.
- a_e_k 4y ago
  Bitbucket lost me when they dropped Mercurial support. If I've got to move to Git, anyway, why should I stick with them?
mulmen 4y ago
RIF’d?
- aGHz 4y ago
  "Reduction in force", similar to a layoff. A layoff happens when the company can no longer afford an employee they'd otherwise like to keep, a RIF happens when the role no longer makes sense and is closed permanently.
- deleted 4y ago
  [deleted]

by pram 4y ago

cestith 4y ago

Did a similar thing happen (minus the new product going away) in the Stash to Bitbucket transition? I also wonder how many people are not moving to Bitbucket Cloud when Server and Data Center are discontinued. Gitlab is still available to be self-hosted with full support.

pram 4y ago
Stash and Bitbucket “cloud” were completely different codebases. It was kind of a unique case. The HipChat “server” was just a weird fork of the “cloud” version. JIRA and Confluent cloud started off as containerized versions of their on-prem versions. Then they did a big rewrite to make them actually multi-tenant. I haven’t been keeping up but Stash was definitely not the priority at the time.
- cestith 4y ago
  Bitbucket Cloud wasn't the immediate successor to Stash, though. There have been Bitbucker Server and Bitbucket DC or whatever they're called for years between the retiring of Stash and the retiring of the on-prem solutions. Where I am we already made the transition from Stash to Bitbucket on-prem (not too long after leaving Gitorious for Stash). When our executives heard "cloud VCS", we bought Gitlab licenses and are moving to that. We also left HipChat for Slack shortly after leaving our own OpenFire server for HipChat. We recently left JSM for Zendesk because it apparently is way easier to get quality statistics out of it. We have shadow IT programs all over the company using something other than Jira even though that's the standard the company provides. We're moving from on-prem Confluence to cloud, but there are still many grumbles about it vs something as simple as FOSWiki or MediaWiki.
a_e_k 4y ago
Bitbucket lost me when they dropped Mercurial support. If I've got to move to Git, anyway, why should I stick with them?

mulmen 4y ago

RIF’d?

aGHz 4y ago
"Reduction in force", similar to a layoff. A layoff happens when the company can no longer afford an employee they'd otherwise like to keep, a RIF happens when the role no longer makes sense and is closed permanently.
deleted 4y ago
[deleted]