11–20 of 408 posts
How about a native client? I think it's safe to assume that Slack has the resources for this.
Give me Grammarly and Dark Mode and then I'll stop using the browser version
Not sure they changed that but this is always at the back of my mind when I see someone use Grammarly via the browser extension:
https://techbeacon.com/security/grammarly-leaks-everything-y...
They say React. How is this a desktop app? It's still in a browser.
How about a native client? I think it's safe to assume that Slack has the resources for this.
I was so happy they had finally gone native. The disappointment is strong. On a side note, SBlack, a lightweight slack client is very impressive on memory usage [1]. 1. https://www.sblack.online/
How does this work? I thought Slack deprecated their IRC gateway; is this all API-based then?
Looks like it just wraps the website in this case.
Yes there are clients that use the API. Slack offers a http rest-like api as well as a websockets realtime api. For example, wee-slack[1] (weechat plugin for slack) and slack-term[2] (curses client in golang).
- The first iteration was largely powered by jQuery(!)
- Every workspace got its own isolated Electron process because they didn't anticipate multiple workspaces in their initial architecture
Honestly it's amazing they got as far as they did with the above limitations. Sounds like this rewrite was sorely needed after their phase of rapid growth. Glad they pulled it off.
They say React. How is this a desktop app? It's still in a browser.
Electron makes it a desktop app. That part has not changed.
No, js/html "applications" are not desktop apps, they're web pages. Doesn't matter how you hide it.
Even though Slack is using react now, they are still using electron under the hood. Which means it can never match the snappiness of a native application like mIRC.