News for hackers. Stuff that matters.
Re:Ask HN: Why is Confluence Wiki Search so bad? by chrisseaton on Monday September 20, 2021 @05:42PM (#28599374)
Atlassian products feel like raw database frontends. I feel like each screen in each Atlassian product is always exactly a database table, being presented to me as an auto-generated form. Might as well use SQL directly.
Re:Ask HN: Why is Confluence Wiki Search so bad? by 0xffff2 on Monday September 20, 2021 @05:53PM (#28599494)
The truly impressive feat (of Jira in particular, but also all of Atlassian's products in general) is how incredibly slow they are. I assume each page somehow touches every single row of every single table in the database because I don't know what else it could be doing to make page loads take so long.
Re:Ask HN: Why is Confluence Wiki Search so bad? by ironmagma on Monday September 20, 2021 @06:30PM (#28599884)
It’s artificially slow to get you to upgrade. Wish I was joking. Thankfully my company uses Clubhouse/Shortcut which is orders of magnitude better.
Re:Ask HN: Why is Confluence Wiki Search so bad? by mdoms on Monday September 20, 2021 @06:58PM (#28600110)
That really couldn't be further from the truth, especially in Jira. Jira keeps virtually every piece of interesting information in a custom field, including built-in fields like issue titles and points (known as system fields but effectively the same thing). Every view you see is the product of a zillion complicated joins across field definitions, field schemes, field values, field permissions and other bits and pieces.
Re:Ask HN: Why is Confluence Wiki Search so bad? by sophacles on Monday September 20, 2021 @06:39PM (#28599954)
Why use a single query languange when one for each view is possible?

- Atlassian probably