zlacker

>>Strang+(OP)
> The attackers gained access to a legacy, third-party cloud file storage system.

I think the answer is ok but the "third-party" bit reads like trying to deflect part of the blame on the cloud storage provider.

>>arbll+Da
The whole codebase & tools at whatever company I ever worked at was using 99% legacy stuff. Its wild...

Often times it would have been easier to rebuild the whole project over trying to upgrade 5-6 year old dependencies.

Ultimately the companies do not care about these kinda incidents. They say sorry, everyone laughs at them for a week and then after its business as usual, with that one thing fixed and still rolling legacy stuff for everything else.

>>zwnow+1e
> Often times it would have been easier to rebuild the whole project

Sure buddy, sure

>>weird-+fg
I inherited a few codebases as solo dev and I am confident in my abilities to refactor each of them in 1-2 months without issues.

I can imagine that in a team that might be harder, but these are glorified todo apps. I am well aware that complete rebuilds rarely work out.