Reducing Slack’s memory footprint

Re:Reducing Slack’s memory footprint by pjmlp on Saturday March 04, 2017 @09:38AM (#13791048)

> ....Facebook and Microsoft building on top of Electron instead of building natively?

JavaScript devs are usually cheaper to hire than C++, Java, Objective-C, Swift, .NET ones.

[ Parent | on HN ]

Re:Reducing Slack’s memory footprint by joekim on Saturday March 04, 2017 @03:49PM (#13792857)

I think VSCode by Microsoft is a good example of Electron done well.

In their case, I don't think it's because their web technology devs are cheaper. I wouldn't be surprised if that team knew multiple platforms and languages. I think it's all about finding the balance between dev costs, making a great product, and getting it out fast on multiple platforms.

[ Parent | on HN ]

Re:Reducing Slack’s memory footprint by pjmlp on Saturday March 04, 2017 @04:49PM (#13793098)

On their case, they want to get a few notches up in the SV popchart culture, top of the pops.

[ Parent | on HN ]

Re:Reducing Slack’s memory footprint by joekim on Sunday March 05, 2017 @06:15PM (#13799469)

Being cool in SV is only so valuable.

[ Parent | on HN ]