That's not what they said. A significant fraction (probably the majority) of Slack's functionality is server-side, not client-side. Even if the client were to be rewritten from scratch, you would not need to replicate 100% of Slack.
But you also don't need to re-implement the entire client. You need to do a significant architectural change for performance improvements, not a complete overhaul. Reasonable people can disagree about whether or not that's feasible for five engineers already familiar with the codebase to do within a few months. Your incredulity at the idea is unwarranted.
No, it's pretty warranted. The 100% I was referring to _was_ just for the clientside. To rewrite that natively (since today it's in js on Electron) is not going to take a couple of months with five engineers.
I don't think it's entirely out of the realm of possibility that could be done, and a couple of months with five engineers was a conservative estimate. $375.000 for twice the devs or twice the number of months is still a shockingly low price to pay.
Hell, throw a few million at it and I can't see why Slack can't be implemented natively on at least iOS, MacOS and Android (especially if parts can still fallback on webviews).
There is absolutely no way in hell that even ten engineers for a couple of months could replicate all of Slack's functionality. Even ten times that much would be a stretch.
They could maybe make a decent chat app prototype in that amount of time. If they are very talented, they might even be able to make a decent chat app MVP that would get some actual users, but there is absolutely no way that they could replicate all of Slack's functionality.
To be clear, we're not talking about replicating all of Slack's functionality. Performance improvements aside from a complete move away from Electron can be considered.
He proposed rewriting Slack natively. Natively implies not javascript. Since Slack is entirely in javascript, a native implementation is by definition a rewrite.
> I'm pretty sure they can hire some talented people, don't you?
Even the most talented construction workers could not build the Empire State Building in a week. It's a little silly to think that these people are like magicians.
Have you looked at Slack's competitors? Slack is arguably the best chat app out there, especially with their UX and the quality of their integrations. It's so presumptious to then tut-tut them suggesting that they "owe their customers better". They're doing very well!
I honestly think slack is a terrible product. IRC is better in every way if you take a few moments and institute logging. Just because they are doing well doesn't mean they are doing well to their customers. It is insanely overpriced, imo.
But you also don't need to re-implement the entire client. You need to do a significant architectural change for performance improvements, not a complete overhaul. Reasonable people can disagree about whether or not that's feasible for five engineers already familiar with the codebase to do within a few months. Your incredulity at the idea is unwarranted.