Earlier 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.
When a rewrite isn’t: rebuilding Slack on the desktop
91–100 of 408 posts
Re: When a rewrite isn’t: rebuilding Slack on the desktop
#92Well there goes my last hope of ever getting a native slack client in my lifetime. I miss hipchat often. They had enough sense to make the client native.
I was very happy when we switched from HipChat to slack.
Re: When a rewrite isn’t: rebuilding Slack on the desktop
#93Earlier quoted context omitted.
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.
Slack is the only web-app I’ve seen that routinely triggers the safari warning about its resource usage/affect on performance. For years slack has been a resource pig on desktop and on the web. So what improvements are you imagining they’ve been working on? Chatting on the internet is hardly such a groundbreaking subject that it can’t be done efficiently.
the ones that are described in the blog post that you're currently commenting on
Re: When a rewrite isn’t: rebuilding Slack on the desktop
#94How about a native client? I think it's safe to assume that Slack has the resources for this.
Nobody has the resources for that. Some companies make OSes, and some companies send rockets to space. Those feats are also powered by thin wrappers over electron. /s 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 Sl…
Re: When a rewrite isn’t: rebuilding Slack on the desktop
#95Earlier quoted context omitted.
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.
If an app is running on its own and not in a web browser, it is a desktop app. The language or framework it is written in does not matter. Do you consider VS Code a web page as well? What about Spotify?
Re: When a rewrite isn’t: rebuilding Slack on the desktop
#96Well there goes my last hope of ever getting a native slack client in my lifetime. I miss hipchat often. They had enough sense to make the client native.
Are you sure HipChat was a native client? At least on MacOS I’m pretty sure it was some web view. If not Electron, one of the others. I was very happy when we switched from HipChat to slack.
Then they switched to QT using WebView (2013) [2].
Then they created Stride using Electron (2017) [3]
Finally they created a partnership with Slack (2018) [4].
[1] https://www.engadget.com/2013/02/14/hipchat-ditches-adobe-ai...
[2] https://techcrunch.com/2013/02/14/with-3500-paying-customers...
[3] https://techcrunch.com/2017/09/07/atlassian-launches-stride-...
Re: When a rewrite isn’t: rebuilding Slack on the desktop
#97Earlier quoted context omitted.
Ripcord [1] is a (native) desktop chat client for Slack and Discord written in C++ and QT. It was posted a few months ago [2] and I’ve been using it since then, it works great. [1] https://cancel.fm/ripcord/ [2] https://news.ycombinator.com/item?id=19617699
interesting - they mention: "Slack connectivity is now available for testing. It's still pretty rough and missing a lot of features." any further insights here? could just try it myself, but slack is our key communication so getting more input would be great
Re: When a rewrite isn’t: rebuilding Slack on the desktop
#98Re: When a rewrite isn’t: rebuilding Slack on the desktop
#99Give me Grammarly and Dark Mode and then I'll stop using the browser version
I'd rather not send my keystrokes to two companies at the same time. 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...
Is there a security-conscious Grammarly alternative?
Re: When a rewrite isn’t: rebuilding Slack on the desktop
#100I know that popular opinion in the Twitterverse is that "Redux is dead", but I note that both Twitter and Slack just released major rewrites that use Redux heavily. I talked about Redux usage stats and comparison with other alternatives in my "State of Redux" talk at Reactathon earlier this year [0], and my post "Redux - Not Dead Yet!" also addresses some of these aspects [1]. Also, quick plug for our current focus.…
Thanks for the articles! We've been using Redux since August of 2016 at Groove. For us, we've found that Redux makes sense when you have state that needs to be shared. If you are dealing with some specific, tightly coupled component state, it sometimes makes sense to keep that particular piece of state local to the component (at least for our use-case). The biggest issues we've run into during our time with Redux hav…
In reality, there should be a good balance between global and local state. I wrote a Redux FAQ entry that tries to give some rules of thumb for determining what state goes where [2].
When we do the docs revamp, hopefully we can make that kind of thinking more explicit.
I'd be very interested in hearing more details on any issues you may be having with React-Redux, and I'm happy to offer advice for you or anyone else on using it better. HN comments aren't a great place for that, but please file an issue for discussion or contact me in the Reactiflux chat channels on Discord in the #redux channel.
I'd also greatly appreciate any feedback folks would have on weaknesses with the current docs, so we can improve those issues with the docs revamp.
We've had open issues to cover writing a "Performance" docs page for a long time, but no one got around to contributing that, and there's been too many other higher priorities for us to write it. My React/Redux links list does have a section of articles on improving Redux perf [3], if that helps, and there's an FAQ section on that topic [4]. In general, connect more components [5], and use memoized selectors [6] to read data and do transforms.
[0] https://redux.js.org/introduction/three-principles
[1] https://redux.js.org/faq/organizing-state#should-i-put-form-...
[2] https://redux.js.org/faq/organizing-state#do-i-have-to-put-a...
[3] https://github.com/markerikson/react-redux-links/blob/master...
[4] https://redux.js.org/faq/performance
[5] https://redux.js.org/faq/react-redux#should-i-only-connect-m...
[6] https://blog.isquaredsoftware.com/2017/12/idiomatic-redux-us...