Standalone Signal Desktop

Re:Standalone Signal Desktop by polpo on Tuesday October 31, 2017 @10:17PM (#15598420)

They could use NW.js instead, which stays up-to-date with the latest Chromium version, including security updates. They usually release on the same day as Chromium. https://nwjs.io/blog/

[ Parent | on HN ]

Re:Standalone Signal Desktop by baby on Wednesday November 01, 2017 @10:26AM (#15601383)

This is interesting, I feel like NW.js has lost the war against Electron, but I haven't closely been following the topic. Can anyone summarize the latest common opinion on the subject?

[ Parent | on HN ]

Re:Standalone Signal Desktop by polpo on Thursday November 02, 2017 @03:05PM (#15613296)

There was a period in late 2014-early 2015 where NW.js stagnated, but since then it's been very actively developed. I found this 2016 comparison pretty even-handed and comprehensive; it'd be nice to see an updated version for 2017. http://tangiblejs.com/posts/nw-js-and-electron-compared-2016...

[ Parent | on HN ]

Re:Standalone Signal Desktop by orange8 on Wednesday November 01, 2017 @10:11PM (#15607272)

I suspect most electron devs haven't even heard of NW.js even though it came first, so there wouldn't even be any comparison to begin with.

[ Parent | on HN ]

Re:Standalone Signal Desktop by orange8 on Tuesday October 31, 2017 @11:23PM (#15598599)

Good answer. Some are just good at putting down solutions, and don't even have the courage to suggest alternatives.

[ Parent | on HN ]