I'm not sure I'd be able to find a better example of not having an understanding of this industry, than someone comparing the upgrade tradition and procedure of an OPERATING SYSTEM to a game.
Actually I spoke about the entire Microsoft Office Suite of products as well, not just the OS. But feel free to ignore that and focus only on what helps you score cheap little points. And for the record, I'm not the one who raised Microsoft in the first instance. I was only pointing out that Microsoft
have released free
major updates for all of their software products, something which was questioned. As I also said, they even went one further and sent the CD out to you
for free if you asked for it, rather than you having to download a massive update. Not all of Microsoft's free updates have been related to security either.
Microsoft have the OS monopoly, and if they're interested in holding on to that
Why, who's going to take their monopoly away from them? That's the whole point of a monopoly. Otherwise it's not a monopoly, is it? In fact Microsoft are in the position where they
don't have to release as many updates (and in fact, have been criticised for holding back various fixes at times). What are you going to do, switch to Unix because an obscure bug related to some software conflict with a program or feature you don't use
wasn't patched in time? That's not to mention all the non-critical updates that are also released like updated help files or the various add-ons for the Microsoft Suite I mentioned earlier.
It's an established standard for every developer of an OS, to constantly improve and evolve their software - because everything depends on a stable OS.
This isn't a process restricted to OS developers. It's an established standard for computer game developers to release updates and fixes for their computer games in the form of patches as well. Blizzard have been constantly "improving and evolving" their games via free patches for years. In fact, everyone in the software industry does it.
Are you kidding me? Do you think quality control equals perfect flawless software?
Who said "perfect flawless software"? No doubt any piece of software is going to have issues because of some obscure conflict with an obscure video card, software, spyware or other issue. However, I'd hope the blindingly obvious (like a translation or obviously poor loading times) would be done right the first time. These aren't hard things to check for. Particularly when your goal is to release a well-polished game, I'd hope some effort was actually put into it. IE: That the developer is satisfied with the product before they release it.
Either CD Projekt were satisfied with what they'd done or they weren't. If they weren't, then we're back to the point Brother None raised earlier. They knowingly released a poorly made or incomplete product. We then run the risk of getting half-finished or incomplete games that desperately need patches on release day - and they'll only be patched if sales are strong enough - because a developer couldn't manage their budget or development process.
The people who suffer under that scenario are the end-users. In fact, non-OS software is potentially even worse than OS software. I'm always using my OS where-as I don't always play The Witcher. Releasing it in an incomplete or inferior state on day-one for "one-time" play-through software potentially means a lot of customers who won't be happy or interested in waiting several months for the update. That means the Developer has even more reason to "get it right the first time".
Saying "why don't you just get everything right the first time?" is like pretending we're not human with flaws, and that we have no economic boundaries to restrict for how long we can work on something before releasing it. You're acting as if developing a game is not an extremely intricate process involving dozens, if not hundreds of people, and there aren't thousands of things that can go wrong.
Your beating up the point just a little here. We're talking about a complete re-translation, loading times, a city of clones and an inventory system that could've been better. Again, these aren't obscure things not easily noticed. They're fairly obvious to anyone who pays them attention, like a beta-tester. If the game crashes the minute you fire it up for example, that's a good indication that something, somewhere is wrong and it should be fixed.
The fact that's its complicated or intricate is mostly irrelevant. If it's too hard for you to make a product that you're satisfied with, within the budget you have, you shouldn't be in business (I'm certain building space shuttles is also hard - it doesn't mean NASA get to say "Aww shucks, we're just human" when one explodes on the platform - they actually review their quality control processes). Regardless of that though, CD Projekt demonstrated their ability to resolve these issues by actually doing it, so technical issues and the "woe-is-me software is hard" argument your making are moot.
You're displaying supreme ignorance of the realities of this business. You think that by simply expecting reality to be different, it can change. You're still pretending like CDPR wanted a flawed product out there - and they're simply stupid for not doing it right.
Nope. I don't think "that by simply expecting reality to be different, it can change". That appears to be a strawman you made up. I think that by implementing some very simple processes things can change.
That's what quality assurance procedures are. It's about having someone responsible for checking the translation. It's about having someone sign off on certain key milestones before the project moves on. In other words it's actually about
doing tangible things in order to bring about change. Not simply "expecting it to happen".
Ignoring the rest of your hyperbole, my point still remains. If CDPR didn't want to release The Witcher in the state it was in, why didn't they engage better quality control processes? Why didn't they insist on an accurate translation? Why did they sign an agreement with Atari that forced them to release a product they were unsatisfied with? If they signed that agreement due to financial circumstances, then once again, it means they knowingly released an inferior product. If they did that, thinking they'd patch it later, then we're now well beyond "software is hard" and back into "we'll patch it if it makes enough sales" territory which is not where I want my computer game developers to be.
I don't want to buy a computer game and then have the honour of gratefully playing the much-improved free updated version in 6 or 12 months time. If I bought it, it means I want to play it relatively soon. If it's not ready to be played, it shouldn't have been released. In fact, as I said, CD Projekt would've saved themselves a lot of time, hassle and money "getting it right" the first time around. I'm certain they could've done with the loading times at least.