[dead]
How's Linear so fast? A technical breakdown
241–250 of 250 posts
Re: How's Linear so fast? A technical breakdown
#242Earlier quoted context omitted.
What if we had a local server running on the same PC, which then relays the request to some shared server on the internet?
That's what a background worker is: a local server managed by the browser and only accessible to pages of the origin domain.
I'm thinking using a local http-server instead of web-workers . The local http server would do all the server-logic except also passing data that needs to be shared to a non-local server.
Re: How's Linear so fast? A technical breakdown
#243Earlier quoted context omitted.
The comparison to Jira is unfair, Jira is known for abysmal performance. Linear was really, incredibly fast. We adopted it in 2021 and it was amazing. Now it’s bloated. That’s the standard path for most software (Zawinski’s Law), and I’m not very excited when they ship another feature. Most of the new stuff isn’t for small players, they’re more of an alternative for medium and large businesses.
I think it depends on your job/role. Unless you're spending literally all day in Jira, I don't think the performance (or even more broadly, the enjoyment) of one's task tracker affects productivity that much.
Understandably, but PMs/POs usually want you to update the board, leave comments, tag things, and so on. Doing that speedily and with keyboard shortcuts in Linear is almost enjoyable.
Re: How's Linear so fast? A technical breakdown
#244Re: How's Linear so fast? A technical breakdown
#245Earlier quoted context omitted.
But it does mean you gracefully degrade so the majority of the company sees the target latency <100ms and the rest of the company sees "not geo-optimized" latency.
Only in the case where there is such a majority of the company that is tightly geolocated. Again, AWS latency us-west-1 to us-east-1 is 70ms. That's absolute best case for one round-trip that does absolutely no work. And it's ignoring the case of anyone outside of continental US. Add in actual server-side work, db interactions, and contention - and you're quickly looking at hundreds of ms.
If your users are truly broadly geodistributed, there's no avoiding hundreds of milliseconds of latency if you want strong consistency. You're fighting the speed of light. You can move the source of truth closer to the majority of users with effort without meaningfully regressing performance for the users who aren't tightly geolocated, so you can treat it as a fairly pure optimization.
Re: How's Linear so fast? A technical breakdown
#246Re: How's Linear so fast? A technical breakdown
#247Earlier quoted context omitted.
There's guaranteed persistence, but there's no guarantee that the host will be up anytime soon. E.g.: I might leave a final reply with all the details on an issue before going on vacation (or maybe I don't work the next day but my colleagues abroad do!). I see that it's properly posted and close the laptop. The reply with be delayed by days or weeks, but the UI indicated that it had been properly saved.
> There's guaranteed persistence There's not. Browsers can delete "persistent" storage at any time. https://developer.mozilla.org/en-US/docs/Web/API/Storage_API...
Quite true. This doesn't negate my point thought: it actually makes the argument stronger.
Re: How's Linear so fast? A technical breakdown
#248Whole blog post is basically: Make a mutation in the clientside, assume it worked, and save in the background.
Well that "make a mutation client-side" phrase is doing a lot of work. Make a mutation to what? The classic server rendered web-app doesn't have any data to make a mutation to . You could try to patch the UI but that would be a huge pita and not really a scalable (in effort) solution. If you have an SPA, you still don't really have data on the client-side. You have a bunch of cached query responses. You can update th…
Make the checkbox turn green. Make the comment appear in the list. Set the date to the new date the user wanted.
That's the mutation.
Whatever your talking about, is irrelevant
Re: How's Linear so fast? A technical breakdown
#249Linear still has broken Back / Forward after literally years! Instead of fixing it they introduced a Pinned Tab feature that doesn’t actually do anything! Absolutely drives me nuts.
update: linear rolled out fixes to these 5 days ago, pretty stoked
Re: How's Linear so fast? A technical breakdown
#250I would always hear about how Linear was fast, but after actually working daily with it, I’ve lost enthusiasm. Search is quite slow, the UI is often clunky (looks good though), “Pulse” is a torrent of noise even at small scale, and I have trouble finding things I need and resort to adding everything to favorites. Early days’ Trello was the best project tracking experience by far.
[flagged]