Reducing Slack’s memory footprint

Re:Reducing Slack’s memory footprint by mdekkers on Saturday March 04, 2017 @11:15AM (#13791474)

They cared more about cost and time to market than performance and technical prowess, and in a business context, that is often a correct trade-off.

Cool when you are starting up and all, but surely they must have a bit more money now, and would be able to do it right?

[ Parent | on HN ]

Re:Reducing Slack’s memory footprint by nemothekid on Saturday March 04, 2017 @12:12PM (#13791785)

When Facebook was hitting performance issues with PHP, they decided to rewrite the entire runtime instead of rewriting in a different language.

If Facebook with its billions decided it was cheaper to rewrite PHP, the cost/benefit analysis must favor optimizing current code than doing a rewrite

[ Parent | on HN ]

Re:Reducing Slack’s memory footprint by mdekkers on Saturday March 04, 2017 @12:43PM (#13791941)

Facebook is Facebook. Slack isn't Facebook, and neither is every other business besides Facebook Facebook decided to rewrite PHP because the CBA worked out for Facebook - that doesn't mean the argument holds true by default for any other situation.

[ Parent | on HN ]

Re:Reducing Slack’s memory footprint by jjnoakes on Saturday March 04, 2017 @11:36AM (#13791571)

But why spend the money to do it from scratch when you can spend less focusing on the pain points?

If your users pay you either way, the cheaper option (from a business point of view) is better.

[ Parent | on HN ]