VMS is used across submarine designs spanning all the way back to 2005. Currently there are 67 submarines actively part of the battle fleet (https://www.nvr.na

VMS is used across submarine designs spanning all the way back to 2005. Currently there are 67 submarines actively part of the battle fleet (https://www.nvr.navy.mil/NVRSHIPS/FLEETSIZE.HTML https://www.nvr.navy.mil/NVRSHIPS/FLEETSIZE.HTML), let's say $3B per submarine, that's $200 *BILLION* dollars of capital expenditure. And it should go without saying that the reason we spend money on submarines is because the missions they go on are that important to the national defense. I think Google has spent less than $200 billion on Google Maps. Between the capital expense and the mission to perform, and the repeated underground collisions, I don't think it's too much to ask that the Navy apply some usability design to support one of the most critical functions of any warship, safe navigation. Because I've used VMS myself and I can attest to everything the author of this article mentions, and it's far from being just a resourcing question: it's inherent to the way the Navy designs, implements and acquires software-based systems. This includes the stuff you mention about hardware (which, oddly, the Navy submarine force had managed to subvert with ARCI sonars, which use commercial servers and a ton of additional spares to meet operational availability needs).