You can see similar examples with say, games on the NES - yes, there were games on the NES that were bugged out and broken, but in general the major releases came with very few bugs (granted they are FAR simpler pieces of software than what is being produced now-a-days), but they also knew exactly what sort of hardware was expected to run their software (the NES system) so it was easier to account for things. They also didn't have the internet to fix mistakes so you had to make sure it was good to go - generally that resulted in more QA testing, but the testers *knew* what environment the game would be running in from day 1. You still see the same thing now where "exclusive" console titles are usually released with a minimum of bugs - because the devs know *exactly* what they're working with from day 1 lol. You can also see this in particular if you get into modding - because modders typically have a minimum of available systems, so if you get in early on any major mod it's going to be a disaster for you most likely unless the game they're modding is very well understood because the person who made it only had 2-3 systems to test it on originally and early adopters get to play guinea pig.
Comments