Hacker News Reader

Comment by Shank | Hacker News Reader

This reminds me of when Slack shutdown its IRC bridge [0], and in a pretty negative way. I get that usage is down, but that tends to happen. Supporting niche users is how you win customer goodwill. The active users of SVN on GitHub clearly aren't going to switch to git, and I can respect the maintenance costs, but they're probably just going to switch to a different provider. For them, their workflow is now in-danger and they have to solve that problem in-addition to whatever they're working on. I always thought it was a lovely little feature GitHub supported, and I'm sad to see it go for this reason.

[0]: https://it.slashdot.org/story/18/03/08/2049255/slack-is-shut...

View on HN

There's some differences as well: GitHub gives a year lead-time, Slack gave two months. IRC and XMPP are a fundamentally different workflows from that horrible web UI, subversion (for basic commands) is not all that different than git (alias svn=git can almost work).

I relate here with Atlassian discontinuing their Jira Server product. I suppose they did the analysis and it wasn’t worth their dev time but there are some customers who CANT move to Jira Cloud for compliance reasons.

So now we are stuck. Stick with unsupported Jira Server, pay $40k/yr for Jira Data Center (!!) or switch with all the business costs associated with that.

They want those subscription revenues and that's as simple as that. In 2-5 years server will be back as never before but you'll be paying a subscription rate.

Sounds about right! And look, so much less expensive than Data Center per year!

Given the datacenter product still exists, I'm fairly sure dev time is not why Atlassian does that.

True that makes sense. Although managing two products vs. one , Server and Data Center, even if they are mostly the same, is not free. As @adra noted, subscription revenue (although there are always support payments) is a likely driver.

To be honest, the timelines Github have gave here are very generous (1 year). Most companies (even big one) these days will shut-down in a short 30 days notice.

> The active users of SVN on GitHub clearly aren't going to switch to git

Seems likely to me that some significant percentage of GitHub SVN usage comes from decade-old scripts running on a build server somewhere. I suspect most of those users will choose to rewrite the script rather than moving to a new provider.

Reply on news.ycombinator.com