4 ms·

Their description of Jira ("like Asana") and Confluence ("like SharePoint") are far off the mark. Confluence does not equate to SharePoint except possibly in t

Their description of Jira ("like Asana") and Confluence ("like SharePoint") are far off the mark. Confluence does not equate to SharePoint except possibly in the limited case of a SharePoint Enterprise Wiki site. SharePoint is more like a web-based RDBMS with both list and file-metadata schemas, a web-based RAD environment to assemble schemas and views (where pages are separate citizens from other data types), centrally managed metadata, and .NET support for enhancement. Asana is task management with folder and hierarchical organization, Jira is practically a RDBMS with a web-based RAD environment, its own de-facto scripting and query languages, and... Wait a minute, it's actually closer to SharePoint than Confluence. Source: I've run a SharePoint training and consulting company for over a decade, and actually use Jira, Confluence and Asana in our own internal systems (because we'd be remiss to naively assume SharePoint is ideal for any of the things we use Jira, Confluence or Asana for, and we're not apologists for Microsoft but rather evangelists for business collaboration). I know very well how both proverbial halves live (the MS crowd and the non-MS crowd) and they're not as different as they'd like you to believe.

cturner 11y ago
Confluence gets sold directly against Sharepoint. The communications department says, "we need to create a corporate strategy for communicating. Dealing with culture is hard, so instead we're going to go and throw money at mechanism." The contenders are sharepoint and confluence. This sales systems is what ruined confluence - they used to have a delightful markup syntax that was a joy to work with, but in order to get checkbox competition against sharepoint they created an awful broken pretend-WYSISYG. Asana and Jira joust for dominance in the all-important "issue-based team work management systems" segment. You can hire agile consultants to tell the people how to do their jobs using it. (actually I think Jira is awesome, but I hate that culture) It speaks well of you that you find this senseless despite your experience.
- underwater 11y ago
  I'm not the biggest fan of markdowns for complex documents. It's fine for little things like adding bold text or inline code blocks, it as soon as you start getting into anything complex it requires help text and constantly checking of the preview window. Good WYSIWYG editors are much more pleasant to use. Quip, Medium and Facebook notes all do a good job of constraining formatting and being predictable.

cturner 11y ago

Confluence gets sold directly against Sharepoint. The communications department says, "we need to create a corporate strategy for communicating. Dealing with culture is hard, so instead we're going to go and throw money at mechanism." The contenders are sharepoint and confluence. This sales systems is what ruined confluence - they used to have a delightful markup syntax that was a joy to work with, but in order to get checkbox competition against sharepoint they created an awful broken pretend-WYSISYG. Asana and Jira joust for dominance in the all-important "issue-based team work management systems" segment. You can hire agile consultants to tell the people how to do their jobs using it. (actually I think Jira is awesome, but I hate that culture) It speaks well of you that you find this senseless despite your experience.

underwater 11y ago
I'm not the biggest fan of markdowns for complex documents. It's fine for little things like adding bold text or inline code blocks, it as soon as you start getting into anything complex it requires help text and constantly checking of the preview window. Good WYSIWYG editors are much more pleasant to use. Quip, Medium and Facebook notes all do a good job of constraining formatting and being predictable.