161 karma · joined February 18, 2011
[ my public key: https://keybase.io/nathanostgard; my proof: https://keybase.io/nathanostgard/sigs/X7uv7WgUDYi93m9cGVZBhR865_G9ovZzAulRfq2NSI4 ]
This restriction was often frustrating, but limited types meant the language was very approachable for beginners. Once a programmer understood the entity and its attributes, they knew what they had to work with. They only needed to find interesting ways to transform data, not interesting ways to organize data.
While sometimes frustrating, the simple type system rarely limited the creativity of developers. This is evident in the wealth of mods that were created for the game. People built Diablo style RPGs [2] with it, racing games [3], and much more.
In Quake's sequels, the modding system grew more flexible (and also more complex). The number of mods seemed to decrease. The amount of mod content for Quake 2 was less than 1, and Quake 3's was far less than 2. The mods that were released were often far more polished, but I think this is representative of the skill level and determination that was required to actually build mods for those games.
Garry's Mod [4] is only modern game I've seen with a similar level of successful modding activity. It also uses a scripting language (Lua). Garry's Mod defines a strict set of structs that you use to interact with the host game engine (effects, entities, tools, and weapons). It feels very Quake-like.
I personally feel like these kinds of restrictions create flatter code, and structure that is easier to hold in my head. I find myself concentrating more on features, rather than on code organization.
[1] http://www.inside3d.com/qcspecs/qc-menu.htm
[2] http://www.inside3d.com/prydongate/
[3] http://www.quakewiki.net/archives/qca/reviews/patch70.htm
These things came together to create some wonderful cinematic moments. I remember one, during a clan match: I was the last member of my team alive, almost completely out of ammo, with three remaining on the enemy team. They rushed into a room to get me. I managed to take down one with the last bullet in my gun, then kicked another out of the room, causing him to drop his hand cannon. I whirled and threw my knife into the face of the third, then grabbed the dropped shotgun and took out the second as he ran back in. I think I had to take a break to recover after that, haha.
I also remember AQ2 not showing which players were alive on either team. I distinctly remember games where I'd use the radio command to report in, only to be met with complete silence... and suddenly realize I was all alone.
Even as a long time CS player, I still prefer AQ2. I'd love to find a modern game like it.
Action Quake 2 (and its spin-offs, namely Action Half Life, and its creators went on to make CS), Rainbow Six, Rogue Spear, Rocket Arena (in all of its incarnations), The Specialists. I think the Existence HL mod did this, too?
There are also a number of games that restrict spawning in other ways, mostly by spawn point or territory control: Gloom, Natural Selection, Day of Defeat, Battlefield, etc.
Effect of sleep loss on C-reactive protein, an inflammatory marker of cardiovascular risk. (http://www.med.upenn.edu/uep/user_documents/dfd10.pdf)
Short Sleep Duration Is Associated with Reduced Leptin, Elevated Ghrelin, and Increased Body Mass Index. (http://med.stanford.edu/school/Psychiatry/narcolepsy/article...)
Neurocognitive Consequences of Sleep Deprivation. (http://www.med.upenn.edu/uep/user_documents/DurmerandDinges-...)
Insomnia with Objective Short Sleep Duration is Associated with Type 2 Diabetes. (http://care.diabetesjournals.org/content/early/2009/07/28/dc...)
Making a game for cheap requires realistic expectations and constraints. You're not going to hit every platform, you're not going to have AAA graphics, and you're not going to have 100 levels. That doesn't mean you can't have a compelling experience.
You can make a polished, successful game with two people and a couple weeks of work, if those people are experienced and you pick the right platform. Canabalt (http://www.adamatomic.com/canabalt/) is an excellent example of this. One developer did the coding, art, and sound. Another developer did the music. The Flash version only took a week to make. When that version was a wild success, a third developer ported it to iOS, which took a couple more weeks.
There are numerous examples of this throughout the indie games community. It takes a smart, experienced designer to make a successful game with such reduced scope, but it can be done.
Class action lawsuits help to ensure that defendants can't get away with doing a small amount of damage to each plaintiff, but a very large amount of damage as a whole. There simply would not be an incentive to bring this sort of litigation if not for this, and companies would likely get away with these kinds of only-slightly-harmful practices. By bringing this sort of class action, the damages can be large enough that the defendant is forced to rethink their actions and make a change in their behavior.
Without class action, the damages would be small enough that the company could ignore it (because so few people were suing), or the legal system would be flooded with an inordinate number of duplicate cases in order to bring an appreciable amount of damage to the defendants.
That said, it would be nice to see some sort of restriction on legal fees, or on who is allowed to bring class action suits (perhaps only consumer advocacy groups, as is true elsewhere in the world).
In the browsers I tested in, it does indeed seem to be significantly faster to copy the array via a normal loop (in Chrome, Firefox, and WebKit mobile, at least). That said, don't start optimizing everything into for loops unless you've identified the code as a bottleneck. It's not worth the additional complexity for a function that's rarely called.