[HN Gopher] Unified Grid: How we re-architected Slack for our la...
___________________________________________________________________
Unified Grid: How we re-architected Slack for our largest customers
Author : GavCo
Score : 30 points
Date : 2024-08-26 10:46 UTC (3 days ago)
(HTM) web link (slack.engineering)
(TXT) w3m dump (slack.engineering)
| PedroBatista wrote:
| Does that architecture will empower that small organization to
| support their app on iOS versions older than 2 years?
| Minor49er wrote:
| Now that this work is complete, maybe they will finally fix
| Slack's input box so that Home and End keys work properly
| ortsa wrote:
| Oh man, I thought I was the only one! It really is maddening to
| not have these work as expected.
| onelesd wrote:
| Ctrl-A and Ctrl-E work. On macos w/ Karabiner you can remap
| Home and End to those for the Slack app.
| DenseComet wrote:
| They put in all this engineering effort, but as a user in
| multiple workspaces in a large enterprise grid, this unified grid
| rework has been a strictly worse user experience.
|
| In a large org, if I am in multiple workspaces, that often means
| they are completely separate contexts and unifying them makes it
| harder to look at exactly what I want.
| wrs wrote:
| All I know is they rearchitected Slack recently so that now the
| mobile app feels asynchronous, in a bad way. Like, you tap on
| things and they don't get marked read -- in the local app! -- for
| _seconds_. Also, the unread count badge doesn't match what you
| see when you open the app.
|
| Slack used to be a really impressive user experience, but it has
| degraded significantly, not in UX design (though that's also
| highly arguable) but in flakiness.
| bob1029 wrote:
| > used to be a really impressive user experience
|
| This is becoming a tale as old as time itself.
|
| I remember when GitHub was so fast I preferred it over Visual
| Studio for browsing the codebase.
| Cthulhu_ wrote:
| That sounds kinda weird but at the same time understandable in
| scalable, worldwide, asynchronous and distributed applications,
| in that "mark read" is not a database query but a task that
| gets added to one or more task queues that eventually lead to a
| data update which in turn eventually leads to a local state
| change.
|
| That said, apps that talk to queue / async based backends like
| that should employ optimistic updates, that is, mark as read
| and presume that goes alright, instead of wait for an update.
| That said, given it's a new architecture, maybe that'll be
| implemented eventually.
| Suppafly wrote:
| >All I know is they rearchitected Slack recently so that now
| the mobile app feels asynchronous, in a bad way.
|
| I feel like Office 365, specifically outlook, is like that
| probably for similar reasons. Unread counts and such on the
| mobile app are never right, and it was fine when our servers
| were on prem and I was using the mobile app.
| GiorgioG wrote:
| Now make the app suck less. It has turned into a needlessly
| complex experience where I have to expend more mental energy than
| should be required to find what I'm looking for.
| JonChesterfield wrote:
| We're probably the end of life phase for slack. Is there a new
| IRC-but-pretty already in place that will be great until a little
| while after it goes public for billions?
|
| edit: I was reasonably impressed with Zulip recently
___________________________________________________________________
(page generated 2024-08-29 23:01 UTC)