Quoted from TechnicalSteam:
Apparently you know nothing of modern day coding practices. That is not possible with a central code repository, pull request and user test.
That is how the web you see here is built. Once in a great while things break but not very often. Good code is easy to maintain and develop.
Any of that is possible. All of those mechanisms you speak of work great in a closed loop with control but once code is open anyone can install it on their machine with any change they want. Sure, it might not be approved for wide-spread distribution by testers/commit managers but that doesn't prevent people from borking their game. That being said, per ltg's point, people can bork their game now without changing the code. Warranty issues still have to function the same way with the manufacturer trying to determine if the issue was caused by the user's negligence and if they want to cover the issue under warranty.
If you have some central maintainer then you have overhead and costs associated with code approval, management, liabilities with "approved" outside code that may still contain flaws, etc. If this were an open source project, sure.
You know pretty darn well no one is going to release code. There is probably very limited interest, no benefit really to the company and opens them up to a whole slew of unwanted issues. Flaws, hacks, backdoors, bad coding practices, etc. would all come to light. Even if minimal and less than the norm would still shed more light than they would care to have shone, I'm guessing.
But, I had the same thought before. Just love to see what they're working with.