Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why Jira Sucks

whyjirasucks.com

Post reply on HN
Print view View original

71–80 of 530 posts

Re: Why Jira Sucks

#71

Post by bitcharmer »

bzb6 wrote: post #66
echelon wrote: post #63

Earlier quoted context omitted.

You might not be familiar with how modern computer graphics work. Objects and textures are loaded into the GPU and managed with an API like OpenGL and shader programs written in languages such as GLSL. Java, in this case, serves as the engine that ties everything together and runs the core game logic. Microsoft rewrote it because they're not a Java shop. Microsoft Games Studio not only uses C#, but their mission is t…

I know exactly how it works. Java runs the game logic, and it does so so slowly that the game skips frames. If you’re claiming that the game logic and the code that runs the graphics are completely untied and run independently that’s wrong. The graphics code cannot paint another frame if it does not know where the objects are because the game logic, written in Java, is lagging behind. C# is much faster than Java. Com…

As opposed to C#, Java (alongside C/C++) is widely used in low-latency applications for high-frequency trading and HPC. Almost no one uses C# for high performance software.

Source: have been doing low-latency engineering for over 15 years.

It's quite apparent your experience with Java language/runtime is outdated and/or shallow. Maybe try reading up on it before making strongly opinionated comments like this?

Re: Why Jira Sucks

#73

Post by smitty1e »

CraigJPerry wrote: post #58

Unpopular opinion: it doesn’t suck. Let me walk that back a bit - I have no experience of the cloudy version which unanimously seems to be derided as slow. Atlassian - you might wanna fix that. Like yesterday. But server (& datacentre) editions - best in class for my money. In terms of features, the Rally / Agile Central (did that just re-brand again?) rollup roadmap view is the only missing feature i crave. Atlassia…

Indeed. It is a tool. The chief issue I encounter is the staff not actually using the tool, whether Jira or otherwise.

If Jira takes a performane hit by lowering the bar for the non-techs, fine.

Just use the tool.

Re: Why Jira Sucks

#78

Post by denysvitali »

catdog wrote: post #70
denysvitali wrote: post #2

Every bullet point says "Missing...", but I feel like the main issue about Jira is that it has waaay to many features, and that it's super slow! The only bullet point I do agree with, is that Jira is missing an easy (or IMHO a minimalist / simple) interface. The tool is a mess, and the people using it are probably also using it in the wrong way, making the whole situation way worse. Don't get me wrong, I like Jira to…

> Every bullet point says "Missing...", but I feel like the main issue about Jira is that it has waaay to many It says "missing" but it mostly talks about those existing features lacking any polish. > and that it's super slow! It is and it really sucks or to quote Firefox "A web page is slowing down your browser, what do you want to do, wait or stop it".

It's funny because I have never seen the mentioned Firefox error on any Jira instance. The problem is mostly server-side: it's slow as hell! I'm personally using go-jira [0], but even that is slow: the problem as I said is not (only) the frontend, but the backend.

[0]: https://github.com/go-jira/jira

Re: Why Jira Sucks

#79

Post by denysvitali »

mulcahey wrote: post #36
wintorez wrote: post #5

All I want from Jira is to allow me to use Markdown.

It has a markup language that accomplishes the same thing effectively but has a completely different syntax. This is super annoying when you are bouncing between pull requests in Atlassian Bitbucket and JIRA tickets. I have tried to create a heading with # only to end up with an at least a hundred times. I imagine this is because JIRA (2002) predates Markdown (2004), or at least its mainstream popularity when GitHub…

Is that an excuse? If we have to make a fair comparison, HTML 5 is newer than both: is that a reason why one shouldn't not update the procuct?

As an additional side note, Jira updates are NOT free. You have to pay for a license fee every year to get the updates + support, but the product unfortunately remains kind of the same: super slow and with missing basic features (e.g: Markdown)

Re: Why Jira Sucks

#80

Post by denysvitali »

CraigJPerry wrote: post #58

Unpopular opinion: it doesn’t suck. Let me walk that back a bit - I have no experience of the cloudy version which unanimously seems to be derided as slow. Atlassian - you might wanna fix that. Like yesterday. But server (& datacentre) editions - best in class for my money. In terms of features, the Rally / Agile Central (did that just re-brand again?) rollup roadmap view is the only missing feature i crave. Atlassia…

> But server (& datacentre) editions - best in class for my money.

Well, performance wise they're as bad as the cloud version. Even when you give the instance a lot of CPU / Memory. The problem is not only the Spring application itself, the DB seems to be missing some indexes or the queries are super badly optimized. God only knows what's really happening under the hood, but my self hosted Jira instance isn't any better (I've tried them both, cloud and on-prem).

Post reply on HN