I think it's typical. The business-minded management folks at tech companies tend to measure success and failure purely in dollars. If the company's financial indicators are good, they assume their trajectory is correct and change nothing. They won't fix or improve existing systems unless an issue is measurably costing them revenue.
In the case of the enterprise shop I work at, our revenue increases year over year, and so technical debt doesn't get addressed unless it causes such trouble that clients threaten to leave. Development gets slower and costlier over time as cruft builds up in the codebase, but that effect can't be measured, so it doesn't exist as far as management is concerned.
In Slack's case, their indicator of success is the giant valuation they just got. Their desktop app is an annoying resource hog, but hey, they have tremendous market share, so it must not really be a problem for users. And if it ain't broke, don't fix it.
In the case of the enterprise shop I work at, our revenue increases year over year, and so technical debt doesn't get addressed unless it causes such trouble that clients threaten to leave. Development gets slower and costlier over time as cruft builds up in the codebase, but that effect can't be measured, so it doesn't exist as far as management is concerned.
In Slack's case, their indicator of success is the giant valuation they just got. Their desktop app is an annoying resource hog, but hey, they have tremendous market share, so it must not really be a problem for users. And if it ain't broke, don't fix it.