at my place of work, we have a lot of files (in the business sense, not the computer sense), and we need to manage them. we used to use this piece of software t

at my place of work, we have a lot of files (in the business sense, not the computer sense), and we need to manage them. we used to use this piece of software that we paid another company to host and manage, and it was a little clunky-looking because it was all written in Java, but it worked great. the software did everything we wanted it to, from importing scanned documents, to allowing us to make forms that can flow through workflows we defined. it was great, except that it required the use of Internet Explorer and Java, but we stuck with it... until the company who made the software was acquired by another company, which is making a similar kind of software, except browser-based... and a billion times more terrible. this new software can be self-hosted or hosted on the company's servers, and we opted to try the self-hosted option out. it's been a complete nightmare. users have to wait 30 seconds or more after clicking "Submit" on a form before it gets submitted. form flows regularly get hung up or vanish completely. right now, the software is using 24.2GB of RAM in IIS, and another 26.8GB for SQL Server, despite being used by only a few dozen users simultaneously—there is absolutely no excuse for this, in anything resembling a sane universe... but this is what we're stuck with for the time being. it's horrible. and the company who makes the software suggests we would get better performance if we went with their hosted option instead of self-hosting—as if that could somehow magically make this piece of utter shit run any better at all whatsoever. but this is where things are right now with software: engineers who have no idea how to engineer things are building layers and layers of abstractions atop each other without giving a single shit about how well it all runs, or how many resources it consumes, or whether the entire functionality of the software you're building could be expressed several order of magnitude more simply by merely stepping back and reevaluating intended functionality and expressing it in code more directly than a billion layers of C# abstractions heaped on top of each other. the funny (but sad) part is, many users, including some of my coworkers, think this is all completely normal, that such simple functionality must be difficult enough for modern computers to run, because their expectations have been set so low by contemporary software. people just don't care if a form takes 30 seconds to submit—maybe if it takes a full minute, then something might be wrong, but 30 seconds? to submit a form to an intranet web server? perfectly acceptable, why would that be a problem, they say. I wish I could be more optimistic about the future of software but at this point it looks like we're kinda just fucked—nobody cares about making good software anymore, and most people have no idea how good, fast, and useful software could be if it was just written a slightly different way than we're taught in college.