Live data from Hacker News

Shrugs.app – A native Slack client for macOS

shrugs.app

151–160 of 236 posts

Re: Shrugs.app – A native Slack client for macOS

#151

Ripcord survived C&D letters because it didn't charge. I feel bad for OP for putting all this work in, because it's really cool - but you're going to get sued.

This is just wrong lol. Cancel has never received C&D orders for Ripcord, and it does charge $20 for the Slack features. Please don't spread misinformation you're not even informed correctly on, dude. If they were going to order a C&D order to Cancel, then they would've done it around the project's start (around 6ish years ago). Actually research this stuff before posting posts like these, plz.

[deleted]

Re: Shrugs.app – A native Slack client for macOS

#152
post #141
post #13

The first thing I looked for was a comparison with the official Slack client in terms of performance, since that's the only reason why I'd consider using this. Numbers for CPU load, memory use, time to perform certain actions, crashes. Doesn't seem to be anything available on the site regarding this, which is a shame.

> crashes I've literally never had or heard of Slack crashing, across Windows, Ubuntu and macOS, regardless of memory available (8-32GB) and use. Do people really have Slack regularly crash on them or is that just something that gets attached to Electron (for some reason).

Slack crashes (unresponsive white window -> hard reload) for me at least once a day on the latest MacOS and Intel MBP, and it seems a common occurrence for many of the coworkers I talk to.

Re: Shrugs.app – A native Slack client for macOS

#153

Earlier quoted context omitted.

An even better reason would potentially be security. Exploits in electron are pretty common, which may be a result of its ubiquity making it a big target. But also it's just a complicated platform to secure.

.

>Slack is one of the most secure Electron apps currently in existence at the moment, they have been...

And from your other comment

>we in the Slack Desktop team

Seems misleading to declare something like this without a disclaimer that you work for the company in question, especially when phrasing it as if you are definitively not a part of said company.

Re: Shrugs.app – A native Slack client for macOS

#154

.

From a UX perspective, it could be useful to have different windows with different recurrent/common conversations. I always interact with the same people and channels, and I find myself constantly Cmd-K to those convos. If I could have several chat windows, I'd just arrange them on my second monitor and have the top-3 laying out there, so I just rotate my head, focus on the right convo, type and submit.

Same as for reading, sometimes I just receive a quick message (like: "changes deployed"). I have to Cmd-K, losing focus of my current conversation just to switch to the other window and see that.

Just an idea tho.

EDIT: this is what I'd do: https://i.imgur.com/kI0Ti9u.png

Re: Shrugs.app – A native Slack client for macOS

#155
post #153

Earlier quoted context omitted.

.

>Slack is one of the most secure Electron apps currently in existence at the moment, they have been... And from your other comment >we in the Slack Desktop team Seems misleading to declare something like this without a disclaimer that you work for the company in question, especially when phrasing it as if you are definitively not a part of said company.

[deleted]

Re: Shrugs.app – A native Slack client for macOS

#156
post #141
post #13

The first thing I looked for was a comparison with the official Slack client in terms of performance, since that's the only reason why I'd consider using this. Numbers for CPU load, memory use, time to perform certain actions, crashes. Doesn't seem to be anything available on the site regarding this, which is a shame.

> crashes I've literally never had or heard of Slack crashing, across Windows, Ubuntu and macOS, regardless of memory available (8-32GB) and use. Do people really have Slack regularly crash on them or is that just something that gets attached to Electron (for some reason).

Slack regularly crashes with an empty window on my Mac. Not like a process crash, but the whole window going empty, needing to quit the process and reopen.

Re: Shrugs.app – A native Slack client for macOS

#157

.

> There is nothing about Electron that constrains it to a single window, what a weird idea.

"Native" means both using the right UI toolkit and being a good citizen by supporting features that are table stakes for apps on the platform. Slack happens to do neither. Look, I understand that UI design is hard, but there's a lot of options that are better than "let's not do it at all". Shrugs has picked one and I think it's all the better for it.

Re: Shrugs.app – A native Slack client for macOS

#158

.

The UI would be the same except the tab would be fixed a specific conversation. Perhaps worth an experiment. I know the purist UX view would want to adapt it to then make the new tabs seamless and so on but I would expect most users just really want to have tabs per conversation or chat or thread and be able to cycle tabs instead of cycling conversations using shortcuts. You are discounting how much comfort the brain gets from a mental model you are used to, and the most common app for people to use is the web browser, which works with tabs for conceptual separation of topics, which is a great analog to different conversations or threads.

Re: Shrugs.app – A native Slack client for macOS

#159

One awesome UI feature of slack is that if you paste a url onto selected test it will automatically create a hyperlink. GitHub markdown does this too. Once you use, it is frustrating when clients don’t implement it. Looking at you, Jira.

Also one of the worst features if you paste hostnames that are now webpages. Always needs ``` - horrible for ops.
Post reply on HN