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

Linear.app

linear.app

Post reply on HN
Print view View original

81–90 of 132 posts

Re: Linear.app

#81

Post by lmm »

aetherspawn wrote: post #63

OK, we are firmware developers who use JIRA in a very advanced way with our clients, and we gave it a go and I just came back here to give the team some feedback because no doubt they are watching this very closely. The killer missing feature for us is that we can't define different issue types. For example, we would typically have issue types like "Requirement", "Bug", "Signal", etc. with different icons and use chi…

> The killer missing feature for us is that we can't define different issue types. For example, we would typically have issue types like "Requirement", "Bug", "Signal", etc. with different icons and use child/parent hierarchies to sort these in a tree with this hierarchy: L1 high-level business requirement, L2 technical breakdown stories, L3 very specific requirement/bug/signal.

Support for this kind of overcomplex use case is what makes JIRA so horrible to use. I very much hope Linear never bloats itself by adding this kind of thing.

Re: Linear.app

#82

Post by chrisfosterelli »

kotlin2 wrote: post #62

I get the appeal of ticketing, I really do. But ultimately, it's a form of control. ICs can't be trusted to figure out what to do on their own, and can't be bothered to talk their team for guidance. And management needs dashboards to track progress. I get it. But I don't want to work on a team where such things are necessary.

Ticketing is a form of organization. If it's being used to control people, that's a problem with the org, not ticketing.

Simply having everyone do what they think is best and hoping they talk enough to sort that all out on their own is great until you have several people unsure what to work on, two people accidentally doing the same thing, and management upset because your features are taking twice or thrice as long as your guestimates.

Eventually you realize that for anything sufficiently complex you need to track what the steps are, who is doing what, and when each part is probably going to be done. You don't want to be a bottleneck, so you make it publicly available to the whole team. Then congrats, you've invented ticketing.

Re: Linear.app

#83

Post by mkl95 »

shubhamjain wrote: post #77

When people crib about how the modern web stack is hodgepodge of buzzwords with little-to-no value, you can show them this. Nearly every page loads within milliseconds, and it's perfectly usable even if you disable JS. The product itself is a great example of how you can deliver a blazingly fast and near-native experience with web technologies. I have been programming web for nearly 15 years. I, too, have issues with…

> I also dislike how (many) senior folks want to pretend that simple HTML/CSS is all it takes to build anything

Although simple HTML/CSS cannot build anything (not even close), simple HTML/CSS with a sprinkle of good JS can get you very far.

Re: Linear.app

#84

Post by j_jochem »

brundolf wrote: post #75

Looks great, but Jira was never getting picked by the users this is marketed to; it's picked by their bosses. It'll be much tougher to sell those people on an alternative.

JIRAs growth strategy was based on developers adopting it without having to talk to their bosses first because it was cheap enough to do so. Nowadays, this probably works differently, but that’s how they initially gained traction.

Re: Linear.app

#85

Post by artman »

inquirer39243 wrote: post #69
enra wrote: post #7

Karri (cofounder) from Linear here. Unfortunately we have been experiencing a DDoS attack the whole afternoon today, so the service is not optimal at the moment and the public website might be slow to load. We are actively blocking and mitigating the attack. https://linearstatus.com Sidenote: While we had these issues, we decided to redirect our homepage to our website Figma file, where we shared iterations for the d…

I couldn't find a mention of it - but is there any plans or ability to self-host? I'm personally not a fan of keeping everything in the cloud. Also are there export options in the event someone wanted to leave the platform?

We unfortunately don't currently have plans to provide self-hosting.

Re: Linear.app

#86

Post by imiric »

Pulcinella wrote: post #41

Breathtakingly fast Built for speed with 50ms interactions and real-time sync. Sorry but 50ms is not breathtakingly fast, especially when native apps and video games can handle multiple interactions at once in 16ms or even faster.

I don't think that's a fair performance bar to set for web apps, or even native apps. The 16ms window for games is used to process input, shuffle data in very fast memory, do calculations, and render a frame on a very fast GPU specifically built for that purpose.

Web apps can also render frames in 16ms, but input often involves fetching data from much slower and unreliable disk or network, processing data on a much slower general purpose CPU, and rendering it via runtimes and frameworks that add considerable overhead. Given all of that, 50ms (20 FPS) does sound very responsive, if maybe not breathtakingly so.

Re: Linear.app

#87

Post by Arcanum-XIII »

aetherspawn wrote: post #63

OK, we are firmware developers who use JIRA in a very advanced way with our clients, and we gave it a go and I just came back here to give the team some feedback because no doubt they are watching this very closely. The killer missing feature for us is that we can't define different issue types. For example, we would typically have issue types like "Requirement", "Bug", "Signal", etc. with different icons and use chi…

I honestly despise Confluence. Jira is kind of OK if you don't create overly complex workflow (they will fail) and avoid using it as a documentation tool (it's not versioned, editing tool are lacking, adding content is quite limited, updating content while fighting field is not fun and finding back the last CR related to a feature is hell).

But Confluence is the worst Wiki I've ever used. It's editor is obnoxious, it's so damn slow, you're losing edit whenever anything happen, tagging is quite often random (recently it added an unwanted "my.favorite" tag to page I'm copying), it's search is broken since the beginning, hierarchical view is broken, creating add on requires to be a high level admin and the implementation is horrible... And I've been forced to use Confluence for 10 years now, in multiple company. None was ever good with it. Heck, here people are screaming to go back to Sharepoint.

Re: Linear.app

#88

Post by Arcanum-XIII »

kotlin2 wrote: post #62

I get the appeal of ticketing, I really do. But ultimately, it's a form of control. ICs can't be trusted to figure out what to do on their own, and can't be bothered to talk their team for guidance. And management needs dashboards to track progress. I get it. But I don't want to work on a team where such things are necessary.

I'd wager that the original idea here is more akin to a list of task, with some info added on top of it. That's how I see it myself.

And yes, I need to have a status. It allows me to warn people outside the dev team if there are any outstanding issues or if we'll be able to soon release something. Communication is key when your team is not its sole customer.

Re: Linear.app

#89

Post by marsouin »

I love Linear, but my problem is involving clients and external users to do QA for instance, the fact that guest accounts (which are often temporary) are priced as full users makes it too expensive for us.

Re: Linear.app

#90

Post by jwr »

aetherspawn wrote: post #63

OK, we are firmware developers who use JIRA in a very advanced way with our clients, and we gave it a go and I just came back here to give the team some feedback because no doubt they are watching this very closely. The killer missing feature for us is that we can't define different issue types. For example, we would typically have issue types like "Requirement", "Bug", "Signal", etc. with different icons and use chi…

Wouldn't tags for for this? It's similar to how I use them.
Post reply on HN