How about a native client? I think it's safe to assume that Slack has the resources for this.
No matter the available resources, maintaining three separate desktop apps as well as a web app would mean fewer features and more bugs across the board. And Linux would probably be left on Electron (with less support attention), if not abandoned altogether.
When a rewrite isn’t: rebuilding Slack on the desktop
21–30 of 408 posts
Re: When a rewrite isn’t: rebuilding Slack on the desktop
#22How about a native client? I think it's safe to assume that Slack has the resources for this.
Re: When a rewrite isn’t: rebuilding Slack on the desktop
#23How about a native client? I think it's safe to assume that Slack has the resources for this.
People seem to forget that C++ and opengl is cross-platform. And there are projects far bigger than slack, like ffmpeg and OpenCV that have existed for decades, always had very fast development cycles, with only a subset of the funding and money that Slack has, and stayed native and close to the metal forever.
A better answer would be, that Slack has deemed the benefits that would result from this as not that important. Or that the current team's expertise cannot handle the task. But they always looking into ways of improving the core product and experience.
Re: When a rewrite isn’t: rebuilding Slack on the desktop
#24How about a native client? I think it's safe to assume that Slack has the resources for this.
As much as I'd love a native app, for a fast moving company with rolling releases it's probably very hard to keep three platforms at the same level especially if you want to do experiments too or roll out features to a small subset.
Name three major feature improvements to Slack in the last three years.
I can think of one, threads, which are a fucking usability disaster and should have been killed immediately. I can't think of a single other major feature.
Re: When a rewrite isn’t: rebuilding Slack on the desktop
#25Re: When a rewrite isn’t: rebuilding Slack on the desktop
#26"We acknowledge that nobody should ever rewrite from scratch... but after five years we're rewriting from scratch because we know better."
Re: When a rewrite isn’t: rebuilding Slack on the desktop
#27Earlier quoted context omitted.
Electron makes it a desktop app. That part has not changed.
Just because you don't see the browser it doesn't mean it's not still there. No, js/html "applications" are not desktop apps, they're web pages. Doesn't matter how you hide it.
Re: When a rewrite isn’t: rebuilding Slack on the desktop
#28How about a native client? I think it's safe to assume that Slack has the resources for this.
No matter the available resources, maintaining three separate desktop apps as well as a web app would mean fewer features and more bugs across the board. And Linux would probably be left on Electron (with less support attention), if not abandoned altogether.
Re: When a rewrite isn’t: rebuilding Slack on the desktop
#29How about a native client? I think it's safe to assume that Slack has the resources for this.
No company has infinite resources. Maintaining native mac and windows apps to appease the few people who have an irrational hatred of electron doesn't make good business sense when those resources could be going work that actually improves their product in a meaningful way.
Re: When a rewrite isn’t: rebuilding Slack on the desktop
#30Earlier quoted context omitted.
Electron makes it a desktop app. That part has not changed.
Just because you don't see the browser it doesn't mean it's not still there. No, js/html "applications" are not desktop apps, they're web pages. Doesn't matter how you hide it.