Skip to content

Comment on Rewriting the Slack Python SDKparent

Comments

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.

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.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.