Live data from Hacker News

Rewriting the Slack Python SDK

slack.engineering

41–50 of 59 posts

Re: Rewriting the Slack Python SDK

#41

Earlier quoted context omitted.

I use the Slack client every day at work on my Mac and it works fine. It is a lot more than a glorified IRC client —- if that’s all it is, then why has Slack built a successful business?

They can sell it to management. The features irc provides and users want are precisely the selling points to authority.

Slack has been mostly bottom up sales, not top down, in my experience.

Re: Rewriting the Slack Python SDK

#42

It still amazes me that Slack, with its infinite resources, hasn’t built native clients. One code base is nice and all, but man I loathe the Electron app.

I've thought the same thing. But also the results speak for themselves: is Slack actually struggling because they don't have native apps? What's the cost to their business bottom line? What motivations would drive it to ever be a priority?

I think this is an example of a community of nerds forgetting that we're something like 0.1% of a product's userbase.

I think the perpetual anti-electron sentiment is a strong example of how you need to be careful not to listen to just your most vocal customers. Otherwise you might triple your engineering load without even a fraction of practical, real life, measurable benefit.

Re: Rewriting the Slack Python SDK

#43

It still amazes me that Slack, with its infinite resources, hasn’t built native clients. One code base is nice and all, but man I loathe the Electron app.

I've thought the same thing. But also the results speak for themselves: is Slack actually struggling because they don't have native apps? What's the cost to their business bottom line? What motivations would drive it to ever be a priority? I think this is an example of a community of nerds forgetting that we're something like 0.1% of a product's userbase. I think the perpetual anti-electron sentiment is a strong exam…

Just because nerds complain doesn't mean doesn't mean "non-nerds" aren't suffering from the same problem except they don't have the technical knowledge to blame it on Slack using Electron, so when their computer is sluggish or runs out of battery in half the expected time they'd just blame it on something else, but the problem itself doesn't magically go away.

Re: Rewriting the Slack Python SDK

#44
post #30

It still amazes me that Slack, with its infinite resources, hasn’t built native clients. One code base is nice and all, but man I loathe the Electron app.

What are some examples of well-written UI-heavy native desktop apps? I'm curious because I see the usual complaints whenever Slack (or another Electron app) is mentioned, and largely agree with them, but what's an app that has actually done native well across Windows/macOS/Linux?

Adobe Photoshop & its friends? Microsoft Office? Just a few examples, I'm sure there's plenty more.

Re: Rewriting the Slack Python SDK

#45
post #40

Earlier quoted context omitted.

Have you actually used the Slack client before ? It's anything but reliable. As you would expect from a glorified IRC client that somehow uses 2GB of RAM (lots of accounts).

Most of their users only have one account at most, because they only work for one company. I think the multiple account feature is relatively neglected.

I only use one account in Safari (not even using the app) and it's way more sluggish than you'd expect, and Safari at some point warns me that the tab is consuming significant amounts of memory and closing it will improve the responsiveness of my Mac.

This is on a top of the line Macbook Pro 2018 with i7 and 16GB of RAM.

Re: Rewriting the Slack Python SDK

#46

Earlier quoted context omitted.

I've thought the same thing. But also the results speak for themselves: is Slack actually struggling because they don't have native apps? What's the cost to their business bottom line? What motivations would drive it to ever be a priority? I think this is an example of a community of nerds forgetting that we're something like 0.1% of a product's userbase. I think the perpetual anti-electron sentiment is a strong exam…

Just because nerds complain doesn't mean doesn't mean "non-nerds" aren't suffering from the same problem except they don't have the technical knowledge to blame it on Slack using Electron, so when their computer is sluggish or runs out of battery in half the expected time they'd just blame it on something else, but the problem itself doesn't magically go away.

Maybe you're right. We would have to measure first. Otherwise we are just doing another thing I hate witnessing: the nerds insisting to the non-nerds that they actually have a problem.

This reminds me of an opinion I heard about why not to do full body scans: you'll inevitably find diagnoses that don't actually matter but will affect the patient's quality of life just by being aware of and inevitably defined by their conditions.

Hmm. On reflection I think this is closely related: treat the patient not the problem.

Re: Rewriting the Slack Python SDK

#47

Earlier quoted context omitted.

I think that having just one common ui system makes a lot of sense. We want web apps to work as well as Native applications, and vise-versa. I support the concept of Electron, but my question is - exactly why is it so bloated? Doesn’t it come with a built-in Chromium? Why is that? Wouldn’t it make more sense if it used the machine’s default browser engine? You would need to look out for different browser versions, bu…

> We want web apps to work as well as Native applications This is fundamentally impossible.

Why?

Re: Rewriting the Slack Python SDK

#48
post #40

Earlier quoted context omitted.

Most of their users only have one account at most, because they only work for one company. I think the multiple account feature is relatively neglected.

I only use one account in Safari (not even using the app) and it's way more sluggish than you'd expect, and Safari at some point warns me that the tab is consuming significant amounts of memory and closing it will improve the responsiveness of my Mac. This is on a top of the line Macbook Pro 2018 with i7 and 16GB of RAM.

If slack is slowing down your laptop (i7 and 16GB ram), it means your laptop is not up to par. I've read that macbooks have terrible thermal throttling under load, maybe that's what's happening to you.

Re: Rewriting the Slack Python SDK

#49

Earlier quoted context omitted.

> We want web apps to work as well as Native applications This is fundamentally impossible.

Why?

Not the parent, but I suppose he is referring to the fact that it’s another layer of indirection, and solve different problems.

It’s akin to saying “we want C to work as well as ASM”, which is kind of like comparing apples to oranges.

Re: Rewriting the Slack Python SDK

#50

It still amazes me that Slack, with its infinite resources, hasn’t built native clients. One code base is nice and all, but man I loathe the Electron app.

Honest question: would you buy a third party native Slack client?

I started an open source Slack client but was struggle to find tractions. Yes the Slack electron client is bad, I hate it with passion but it just works. And most of the users I surveyed think so too. Either they’re not using Slack at all, or they just don’t care if it’s electron/web-based/slow (Stockholm syndrome?).

Post reply on HN