Agreed - you Americans are (were?) lucky - in Canada, we have the Space channel, and that description "The place bad programing goes to die" hits the nail right on the head. I hope your Sci-Fi doesn't become the same.
The new transformers comic books are startlingly good acutally. DreamWave has finally gotten their act together with that shit. I highly recommend The War Within and Armada comic-book TF lines.
This also works for 2k, but you have to log in on admin and enable the service. There's also third party apps (mostly open source, actually) for soundcard or even full-OS emulation. If you're really into the old games, you'll also need to get MoSlo and TPPATCH because many were made on an old compiler that has clock issues with Pentium II+ clockspeeds.
Dune wasn't really a re-make. It was deliberately designed to _ignore_ the first film. It was just a second direct adaptation from Herbert's Book (which, IMHO, while was closer to the original content of the book, still missed the point).
Technically speaking, these aren't cheats. They're not really 'sploits. These players are playing by the rules. Its just that the rules suck. Quake is not a well-designed game - that's why its so "skill oriented" on skills that are orthogonal from regular gameplay. The designers didn't think enough, didn't worry enough about how the game would work. See www.sirlin.net for a good discussion of "cheating".
Actually, I find this to be true of all team-based FPS games. In deathmatch, you spend most of your time fighting - but in CTF and others types, you spend a lot of your time just getting from A to B. In games like this, you really, really feel the top speed of the FPS runner, and really get bored by the simplistic movement model.
That being said, I think the accidental QuakeWorld approach of jumping everywhere like a friggin rabbit drives me up the wall. I much preferred Doom's movement model - for those who haven't had the pleasure, try out Doom Legacy with the autorun off - the sheer speed that game has, plus the extremely slippery physics model, is a startling experience, and oodles of fun. Oh, the crap we missed just because Romero was too dumb to include an autorun option.
For the record, my fave is UT2k3, where the funny movement tricks (air-jump, wall-kick, etc) were actually designed intentionally, not little sploits of bugs.
Plus, I've never been a fan of the "pro" Q3 concept that on spawn a player must be castrotti. Yes, Q3's minigun was overpowered - but that was because it was a hitscan weapon, and hitscan weapons always become more powerful at pro levels. I'd prefer a weapon of more limited usefulness, but with a deterrent power that actually allows the player to stand a chance at getting guns. Shogo, while an otherwise shitty game, had a good approach to that problem - you could transform to an unarmed highspeed vehicle. It meant that you usually had a good ability to run away if the action got too hot - but people could chase you and see if they could get a shot in too.
BF1942? Have you not seen the orgasmic joy that is UT2k3? My only problem with 2k3 is map design. They finally made an engine that does both sexy FPS action and huge battlefields, and made the bad assumption that FPS action would go well with huge battlefields everywhere. The level design is quite often the pits. Some of teh air maps are good (which has always been DE's forte) but the corridor maps just don't feel as good as my faves from Q2.
Anyhoo, for fun physics + retro gaming, real men play Doom Legacy. Do you remember how slippery and fast doom run was? Autorun with that is insane. Still, you need weaponmods to make the weaponbalance usable, but its good fun.
You know what I think the problem is - not enough people have disconnected the individuals and the administration responsible. Yeah, it'd suck to be her. But we make fun of the media circus, the manipulative government through her.
The whole situation was the literal real world life-imitates-art adaptation of the film Wag the Dog (except she didn't rape a nun). The hospital was deep in friendly territory, with hospital staff treating her better then their own patients because they _knew_ who was in control and wanted to be on the right side.
Instead of picking her up carefully and peacefully like they had every opportunity to, the US endangered her life by using a commando raid (full of commandoes who probably didn't even know where they were) to fish her out.
What would have happened if the rescue raid had gone wrong? Whose fault would it have been? Who would have been blamed? And what would have been thought of those who complained? This is the thought-power of the current administration.
Yeah, sucks to be her. But we're tired of being fucked with. Its not personal for us about her - I think the average American has every right to send her a "Get Well Soon" card and crack jokes and bitch at the same time, the same way they should have about other national tragedies. It is a multi-faceted view of the situation that keeps us sane, and keeps us responsible. To submit to seeing a problem only one way is to be a sheep.
Whoever modded this flamebait is clueless. I have heard a variation of each and every one of these on multiple occasions from my fiancee. I love her to death, but these comments hit the nail on the head.
Likewise, putting money in the hands of the people does not necessarily stimulate the economy. They could simply invest it in offshore firms, or money-market speculation. In general, putting money in the hands of lower-middle class (who put the money right into the economy) is more effective at market stimulation then putting it into the rich. After all, with the money in the economy, it will trickle up to the rich anyways - if they get a bigger piece of the pie and the pie is bigger, then they'll get it. So lets have more of the "trickle up" effect then.
Hm. After that I'm not sure if this is satire or not.
Well event thought one of your closed-minded buddies modded down my wholly factual post, I'm going to back it up.
And you never answered my question: does that figure include monies to prop-up failing businesses that the military still needs as defense contractors? Its not a complicated question.
from 5 seconds on google: http://www.cato.org/dailys/11-20-96.html http://www.cato.org/pubs/pas/pa-350es.html http: //www.ctj.org/html/welfar99.htm
I'm not referring to the defense contracts themselves - that's legitamate (if incompetent) commerce. I'm referring to the free payola the US pays them separate from actually purchasing products, just because they need to keep the business alive.
You don't really do your argument too much justice either by not reading.
There are other possible conventions that would work too. Actually, when you get into overriding dereference, then there is a big difference between the arrow operator and the . operator.
I'd almost think multiple dots would be the way to go.
For example c.d (*c).d == c->d == c..d (**c).d == (*c)->d == c...d
Either that or a high-precedence version of the rereference operator. Having the dereference operator lower precedence then the member operator is what causes those ungodly messes of brackets.
Notice that the arrow operator kinda barfs on pointers to pointers (and I use them a lot - particularly when doing strange things with STL). Thats one of the things I have a big problem with in C++ - the friggin arrow operator is an obvious kludge.
The STL rears an ugly head of many problems - the fact that an object must be copy-perfect is a good example, making putting auto_ptr's into it impossible, no matter how nice it would be.
My biggest problem is the member operator - while its nice to have the difference between classes and instances plainly visible, it makes using namespaces fugly. You either fully import the namespace (thus defeating the entire purpose of having a namespace) or you use the nasty::operator.
In java, I got used to deeply nesting my libraries for good organization. Yes, it.was.long.to.my.function but it was very readable, and the function could be aliased if you needed it (good feature). When I code in C++ it becomes NPyTp::NGizmo::New which is such a pain, and ugly. There's a place I'd like a simpler operator.
Actually, many of us don't really remember JFK all that fondly. JFK captured the country as a whole - but his gloss kinda fades when you look to closely at him. I think Carter was a much better Democrat president. For one thing, he was just about the only Prez who didn't suck up to the Israelis.
Are you counting the fat corporate welfare payments to keep defense contractors afloat because their business has long since fallen apart but Uncle Sam still needs them to make parts?
I can't help but notice that an awful lot of those seem to be Republican presidents. Doesn't quite seem even, now does it? I guess Carter's got a sub tho.
Actually, given the recent history of the US, I think you can justify the aircraft carrier. Now that the US has committed itself to world domination, I think such things will come in handy.
That being said, I think the recent foreign policy is what needs to be questioned, not the USS Ronald Reagan.
Well, in this case, even reasonable Americans can have a problem with Reagan. The man ran the country into the shitter, and got off scot-free. Naming a carrier after him would be like naming a courthouse after Nixon.
No - we need an OS/windowing system that forces coders to make things usable automatically. Command line and graphical launch should be the same thing from a developer standpoint - instead of having to pop-over to the command line, the user should be able to pop-open a constext menu for the run-parameters of a program, and see limited options, not just an ambiguous text-passing system. It should be more convenient to write a configuration system through a graphical widget window then through a text editor. Basically, I think code should move away from the simple text config file, and more into a database-style concept of a header that defines widgets. So, the configuration simply becomes an onscreen list of widgets - with no text file to get confused by. Sure, if the coder leaves out the doctext then this thing is confusing - but at least widgets will give you a vague idea what the control does.
The problem is that all major OS's are gradually evolutionary growths from the 80's. None are actually "designed".
For embedding into applications - the application should be handling all the content moving in and out of the scripting engine. Alternately, to allow the user to develop a secure, proprietary filesystem or file access or system calling system within an extension module, independant of the unsafe main filesystem. This puts the burden of security on the person building the application - not the end user who will be scripting (which is unsafe) or on Python itself.
Slashdot Mirror
Agreed - you Americans are (were?) lucky - in Canada, we have the Space channel, and that description "The place bad programing goes to die" hits the nail right on the head. I hope your Sci-Fi doesn't become the same.
The new transformers comic books are startlingly good acutally. DreamWave has finally gotten their act together with that shit. I highly recommend The War Within and Armada comic-book TF lines.
This also works for 2k, but you have to log in on admin and enable the service. There's also third party apps (mostly open source, actually) for soundcard or even full-OS emulation. If you're really into the old games, you'll also need to get MoSlo and TPPATCH because many were made on an old compiler that has clock issues with Pentium II+ clockspeeds.
Dune wasn't really a re-make. It was deliberately designed to _ignore_ the first film. It was just a second direct adaptation from Herbert's Book (which, IMHO, while was closer to the original content of the book, still missed the point).
Technically speaking, these aren't cheats. They're not really 'sploits. These players are playing by the rules. Its just that the rules suck. Quake is not a well-designed game - that's why its so "skill oriented" on skills that are orthogonal from regular gameplay. The designers didn't think enough, didn't worry enough about how the game would work. See www.sirlin.net for a good discussion of "cheating".
Actually, I find this to be true of all team-based FPS games. In deathmatch, you spend most of your time fighting - but in CTF and others types, you spend a lot of your time just getting from A to B. In games like this, you really, really feel the top speed of the FPS runner, and really get bored by the simplistic movement model.
That being said, I think the accidental QuakeWorld approach of jumping everywhere like a friggin rabbit drives me up the wall. I much preferred Doom's movement model - for those who haven't had the pleasure, try out Doom Legacy with the autorun off - the sheer speed that game has, plus the extremely slippery physics model, is a startling experience, and oodles of fun. Oh, the crap we missed just because Romero was too dumb to include an autorun option.
For the record, my fave is UT2k3, where the funny movement tricks (air-jump, wall-kick, etc) were actually designed intentionally, not little sploits of bugs.
Plus, I've never been a fan of the "pro" Q3 concept that on spawn a player must be castrotti. Yes, Q3's minigun was overpowered - but that was because it was a hitscan weapon, and hitscan weapons always become more powerful at pro levels. I'd prefer a weapon of more limited usefulness, but with a deterrent power that actually allows the player to stand a chance at getting guns. Shogo, while an otherwise shitty game, had a good approach to that problem - you could transform to an unarmed highspeed vehicle. It meant that you usually had a good ability to run away if the action got too hot - but people could chase you and see if they could get a shot in too.
BF1942? Have you not seen the orgasmic joy that is UT2k3? My only problem with 2k3 is map design. They finally made an engine that does both sexy FPS action and huge battlefields, and made the bad assumption that FPS action would go well with huge battlefields everywhere. The level design is quite often the pits. Some of teh air maps are good (which has always been DE's forte) but the corridor maps just don't feel as good as my faves from Q2.
Anyhoo, for fun physics + retro gaming, real men play Doom Legacy. Do you remember how slippery and fast doom run was? Autorun with that is insane. Still, you need weaponmods to make the weaponbalance usable, but its good fun.
No, not a hover chair. Hawk-man uses an exoskeleton
You know what I think the problem is - not enough people have disconnected the individuals and the administration responsible. Yeah, it'd suck to be her. But we make fun of the media circus, the manipulative government through her.
The whole situation was the literal real world life-imitates-art adaptation of the film Wag the Dog (except she didn't rape a nun). The hospital was deep in friendly territory, with hospital staff treating her better then their own patients because they _knew_ who was in control and wanted to be on the right side.
Instead of picking her up carefully and peacefully like they had every opportunity to, the US endangered her life by using a commando raid (full of commandoes who probably didn't even know where they were) to fish her out.
What would have happened if the rescue raid had gone wrong? Whose fault would it have been? Who would have been blamed? And what would have been thought of those who complained? This is the thought-power of the current administration.
Yeah, sucks to be her. But we're tired of being fucked with. Its not personal for us about her - I think the average American has every right to send her a "Get Well Soon" card and crack jokes and bitch at the same time, the same way they should have about other national tragedies. It is a multi-faceted view of the situation that keeps us sane, and keeps us responsible. To submit to seeing a problem only one way is to be a sheep.
Wait - I forgot about Julia Roberts. Second strangest.
Complete with your orz quote, I dub you the strangest gamer ever. SC2 r0x.
I use Pxtl, 0gre (with zero) or Detritus Metropolis.
Anikin becomes a bad guy.
Whoever modded this flamebait is clueless. I have heard a variation of each and every one of these on multiple occasions from my fiancee. I love her to death, but these comments hit the nail on the head.
Likewise, putting money in the hands of the people does not necessarily stimulate the economy. They could simply invest it in offshore firms, or money-market speculation. In general, putting money in the hands of lower-middle class (who put the money right into the economy) is more effective at market stimulation then putting it into the rich. After all, with the money in the economy, it will trickle up to the rich anyways - if they get a bigger piece of the pie and the pie is bigger, then they'll get it. So lets have more of the "trickle up" effect then.
Hm. After that I'm not sure if this is satire or not.
Well event thought one of your closed-minded buddies modded down my wholly factual post, I'm going to back it up.
: //www.ctj.org/html/welfar99.htm
And you never answered my question: does that figure include monies to prop-up failing businesses that the military still needs as defense contractors? Its not a complicated question.
from 5 seconds on google:
http://www.cato.org/dailys/11-20-96.html
http://www.cato.org/pubs/pas/pa-350es.html
http
I'm sure you can find more.
I'm not referring to the defense contracts themselves - that's legitamate (if incompetent) commerce. I'm referring to the free payola the US pays them separate from actually purchasing products, just because they need to keep the business alive.
You don't really do your argument too much justice either by not reading.
There are other possible conventions that would work too. Actually, when you get into overriding dereference, then there is a big difference between the arrow operator and the . operator.
::operator.
I'd almost think multiple dots would be the way to go.
For example
c.d
(*c).d == c->d == c..d
(**c).d == (*c)->d == c...d
Either that or a high-precedence version of the rereference operator. Having the dereference operator lower precedence then the member operator is what causes those ungodly messes of brackets.
Notice that the arrow operator kinda barfs on pointers to pointers (and I use them a lot - particularly when doing strange things with STL). Thats one of the things I have a big problem with in C++ - the friggin arrow operator is an obvious kludge.
The STL rears an ugly head of many problems - the fact that an object must be copy-perfect is a good example, making putting auto_ptr's into it impossible, no matter how nice it would be.
My biggest problem is the member operator - while its nice to have the difference between classes and instances plainly visible, it makes using namespaces fugly. You either fully import the namespace (thus defeating the entire purpose of having a namespace) or you use the nasty
In java, I got used to deeply nesting my libraries for good organization. Yes, it.was.long.to.my.function but it was very readable, and the function could be aliased if you needed it (good feature). When I code in C++ it becomes NPyTp::NGizmo::New which is such a pain, and ugly. There's a place I'd like a simpler operator.
Actually, many of us don't really remember JFK all that fondly. JFK captured the country as a whole - but his gloss kinda fades when you look to closely at him. I think Carter was a much better Democrat president. For one thing, he was just about the only Prez who didn't suck up to the Israelis.
Are you counting the fat corporate welfare payments to keep defense contractors afloat because their business has long since fallen apart but Uncle Sam still needs them to make parts?
I can't help but notice that an awful lot of those seem to be Republican presidents. Doesn't quite seem even, now does it? I guess Carter's got a sub tho.
Actually, given the recent history of the US, I think you can justify the aircraft carrier. Now that the US has committed itself to world domination, I think such things will come in handy.
That being said, I think the recent foreign policy is what needs to be questioned, not the USS Ronald Reagan.
Well, in this case, even reasonable Americans can have a problem with Reagan. The man ran the country into the shitter, and got off scot-free. Naming a carrier after him would be like naming a courthouse after Nixon.
No - we need an OS/windowing system that forces coders to make things usable automatically. Command line and graphical launch should be the same thing from a developer standpoint - instead of having to pop-over to the command line, the user should be able to pop-open a constext menu for the run-parameters of a program, and see limited options, not just an ambiguous text-passing system. It should be more convenient to write a configuration system through a graphical widget window then through a text editor. Basically, I think code should move away from the simple text config file, and more into a database-style concept of a header that defines widgets. So, the configuration simply becomes an onscreen list of widgets - with no text file to get confused by. Sure, if the coder leaves out the doctext then this thing is confusing - but at least widgets will give you a vague idea what the control does.
The problem is that all major OS's are gradually evolutionary growths from the 80's. None are actually "designed".
For embedding into applications - the application should be handling all the content moving in and out of the scripting engine. Alternately, to allow the user to develop a secure, proprietary filesystem or file access or system calling system within an extension module, independant of the unsafe main filesystem. This puts the burden of security on the person building the application - not the end user who will be scripting (which is unsafe) or on Python itself.
Seconded.