Come on, the guy was using EXAMPLES, not saying that all of the examples would be in the same mod.
As for your supposed gravity gun "imbalance": you cannot pick up a dumpster or, indeed, anything larger than a file cabinet or book case. Second, it actually takes some aiming skill to kill someone with a thrown file cabinet -- it's not a skill-free weapon. Finally, there aren't always throwables lying around, and even when there are, they don't jump into your gun instantaneously. I must have killed 100 people with the SMG or the Magnum from close range while they desperately tried to suck up a file cabinet from 50 yards away.
Basically, the balance is great and allows players a real freedom that just isn't in any other game. So stop being wrong.
Not saying strong typing is inherently better, but that sometimes you REALLY, REALLY want to know if you're doing something stupid at compile time instead of run time.
Re:Plenty of differences
on
Java 1.5 vs C#
·
· Score: 4, Informative
Behold BigInteger and its evil twin, BigDecimal. They laugh at silly-big numbers.
CC transactions are handled by a secure third party through Steam. The CC transaction is done through a 128-bit SSL encrypted stream, exactly the same as an https:// transaction. At no time does Valve store billing information on their servers. Buying over Steam is no more risky than buying anything else over the internet, and probably less so.
If you'd bothered to read about this on steampowered.com instead of talking out of your ass, you might not have sounded like such an idiot.
I'm glad someone other than me (who can get published on a site slashdot will link to) said it:
Compilers shouldn't generate warnings, they should generate errors.
It's time to stop holding the programmer's hand. If I write a C program that makes 5 malloc() and 4 free(), the compiler should notice that and say, "Gee, you have a memory leak here" and refuse to compile. It should NOT say, "Well, what you're doing is provably unsafe and probably not what you want, but yes sir Mr. Developer, I'll happily crash the system for you!" It is NEVER correct to write unsafe code.
I understand that there is a certain laxness built into C to make it easy to port to multiple platforms, etc., but these were compromises made in the early 70s, ffs. How long must we live with choices made under circumstances that became outdated 20 years ago?
Most of the Jedi who died at Geonosis were woefully unprepared for any sort of large-scale battle. Note that the survivors were all either Jedi Council members or extremely skilled Knights. (And Anakin, cause he's The Chosen One and stuff.) Remember the guy who tries to jump Dooku in the gallery and then gets blasted by Jango? And then remember how Dooku flat-out OWNS both Obi-Wan and Anakin with his lightsaber?
Sad fact is that the Jedi have begun to lose their connection to the Force and their lightsaber training is pretty pathetic. Too many Jedi neglect their training and barely know Form VI, which is already the weakest of the lightsaber styles. Mace Windu has a deeper understanding of the Force than anyone save Yoda, and even without his lightsaber he's still dangerous. It all hangs together perfectly.
*rereads last two paragraphs*
Wow, I'm approaching geek nirvana. Smells like teen spirit.
Um, I work for Disney Internet Group. Perhaps you've heard of go.com and friends, including disney.com, abcnews.com, espn.com, movies.com, and ToonTown.
Everything -- *EVERYTHING* -- web-related runs on our custom servlet engine/web template languages. (They are open source; you can get them at teatrove.sf.net. All 100% Java and not substantially changed since 1999. Would you like to guess at the number of terabytes we serve daily, or the number of millions of unique page views?
Here in the real world, on the front lines, Java has been more than adequate for the needs of one of, if not *the*, biggest and most popular web rings in the world. I'm not saying it's the only solution or that it's perfect, but Java has proven itself more than capable of handling some seriously heavy-duty shit.
If you feed bytecode compiled by 1.4 to a 1.5 VM, it will work just as it did without any alteration. So when the happy customer upgrades, it won't break. Upgrading a VM *will not break* previously working code.
By default JDK 1.5 compiles source into bytecode suitable for 1.4 VMs. That means that unless you specifically use "-target 1.5", any use of newly minted keywords like "enum" won't conflict with old variable names.
If one fine day the developer decides that he wants to use 1.5 features, he can search and replace the variable name and use -target 1.5, *but he is not forced to do that until he wants to*.
That was my first thought too. There must be some mirrors that didn't update, or have the last known good copy of these files. I assume mirroring was shut off as soon as they discovered the breach. Some server in Russia somewhere has the known good distributions.
Okay, this kind of shit makes me want to start throwing bricks. Cracking the GNU FTP server? Is nothing sacred anymore? I feel like someone burned down a church.
They've done so much for humanity and some utter twit decides to compensate for his bad childhood by taking their server down.
*goes off to dock another point from his faith in humanity*
Or, as I fervently hope is the case, IBM wants to put an end to this proprietary UNIX shit once and for all. Maybe even score a major victory on the GPL front. They think they will have to deal with these kinds of lawsuits from all kinds of people if the base issues are not dealt with in an authoritative and final manner now. Therefore, they're assembling a crushing weight of lawyers and facts to destroy SCO's case point-by-point, leaving other parties no foundation on which to build another case.
Filing for summary judgment and/or dismissal would get this case out of the courts, but what happens in six months when, say, Microsoft buys SCO and decides to attack IBM over Linux? (Hey, it could happen.)
Plus, the longer SCO talks, the more ridiculous they look and the more they open themselves to harassment suits. Let 'em dig their own grave.
No worries, the hired goons just visit each of them and ask to see the Windows XP folder with the claimed serial number sticker on the back. Joe Sixpack will meekly hand it over and Joe Script-Kiddie will silently vanish into the Microsoft Dungeons.
but there are some things, even in our geeky computer-loving world, that need to be done in person. If you're going to ask a girl to marry you, you do it *in person*, looking her *in the eyes*, *on your knees*, like a man. You owe both of you that much.
Anyway, best of luck to both of you and much happiness to you.
ILM is pulling 60-hour weeks (so I hear) on finishing Episode II. The new movie, if it's started shooting, needs to be in postproduction by the beginning of February. There simply isn't time.
Plus, if you were at ILM, would you rather work on Episode II or on Star Trek X? (Ideally, you'd want to do them back to back, but if you had to make a choice...)
Well, in the original script, Kirk was shot by Soran (the bad guy) with some kind of phaser weapon. I think he died after a climactic fight between Picard and Soren. Not sure why they changed it, but it wouldn't have been any better. What a stupid way to kill one of my heroes.:(
Actually he just said "port 80" -- I inferred outgoing from context. But you're right. That would be rather dumb, wouldn't it?:) Cheerfully withdrawn.
Verizon DSL is NOT THAT EVIL
on
Broadband Crackdown
·
· Score: 4, Informative
Verizon *DOES NOT BLOCK* outgoing port 25 *OR* port 80! I've been running my own mail server off the standard DSL offering, $40 a month, for almost a month now and never one hint of problems. I can send mail anywhere. I can telnet to port 25 on any Internet-accessible mail server.
And correct me if I'm wrong, but if Verizon blocks outgoing port 80, wouldn't that put a bit of a dent in most popular web browsers?
For the love of God, try to be a little accurate! There are plenty of real problems to bitch about!
Slashdot Mirror
I just hope it doesn't suck like the OTHER Xen.
Wrong.
Come on, the guy was using EXAMPLES, not saying that all of the examples would be in the same mod.
As for your supposed gravity gun "imbalance": you cannot pick up a dumpster or, indeed, anything larger than a file cabinet or book case. Second, it actually takes some aiming skill to kill someone with a thrown file cabinet -- it's not a skill-free weapon. Finally, there aren't always throwables lying around, and even when there are, they don't jump into your gun instantaneously. I must have killed 100 people with the SMG or the Magnum from close range while they desperately tried to suck up a file cabinet from 50 yards away.
Basically, the balance is great and allows players a real freedom that just isn't in any other game. So stop being wrong.
Most of that unlocking time is the decryption and hard disk activity, not Steam network activity.
Behold BigInteger and its evil twin, BigDecimal. They laugh at silly-big numbers.
Ignorant.
CC transactions are handled by a secure third party through Steam. The CC transaction is done through a 128-bit SSL encrypted stream, exactly the same as an https:// transaction. At no time does Valve store billing information on their servers. Buying over Steam is no more risky than buying anything else over the internet, and probably less so.
If you'd bothered to read about this on steampowered.com instead of talking out of your ass, you might not have sounded like such an idiot.
I'm glad someone other than me (who can get published on a site slashdot will link to) said it:
Compilers shouldn't generate warnings, they should generate errors.
It's time to stop holding the programmer's hand. If I write a C program that makes 5 malloc() and 4 free(), the compiler should notice that and say, "Gee, you have a memory leak here" and refuse to compile. It should NOT say, "Well, what you're doing is provably unsafe and probably not what you want, but yes sir Mr. Developer, I'll happily crash the system for you!" It is NEVER correct to write unsafe code.
I understand that there is a certain laxness built into C to make it easy to port to multiple platforms, etc., but these were compromises made in the early 70s, ffs. How long must we live with choices made under circumstances that became outdated 20 years ago?
Most of the Jedi who died at Geonosis were woefully unprepared for any sort of large-scale battle. Note that the survivors were all either Jedi Council members or extremely skilled Knights. (And Anakin, cause he's The Chosen One and stuff.) Remember the guy who tries to jump Dooku in the gallery and then gets blasted by Jango? And then remember how Dooku flat-out OWNS both Obi-Wan and Anakin with his lightsaber?
Sad fact is that the Jedi have begun to lose their connection to the Force and their lightsaber training is pretty pathetic. Too many Jedi neglect their training and barely know Form VI, which is already the weakest of the lightsaber styles. Mace Windu has a deeper understanding of the Force than anyone save Yoda, and even without his lightsaber he's still dangerous. It all hangs together perfectly.
*rereads last two paragraphs*
Wow, I'm approaching geek nirvana. Smells like teen spirit.
Um, I work for Disney Internet Group. Perhaps you've heard of go.com and friends, including disney.com, abcnews.com, espn.com, movies.com, and ToonTown.
Everything -- *EVERYTHING* -- web-related runs on our custom servlet engine/web template languages. (They are open source; you can get them at teatrove.sf.net. All 100% Java and not substantially changed since 1999. Would you like to guess at the number of terabytes we serve daily, or the number of millions of unique page views?
Here in the real world, on the front lines, Java has been more than adequate for the needs of one of, if not *the*, biggest and most popular web rings in the world. I'm not saying it's the only solution or that it's perfect, but Java has proven itself more than capable of handling some seriously heavy-duty shit.
No, it will not be any sort of problem.
If you feed bytecode compiled by 1.4 to a 1.5 VM, it will work just as it did without any alteration. So when the happy customer upgrades, it won't break. Upgrading a VM *will not break* previously working code.
By default JDK 1.5 compiles source into bytecode suitable for 1.4 VMs. That means that unless you specifically use "-target 1.5", any use of newly minted keywords like "enum" won't conflict with old variable names.
If one fine day the developer decides that he wants to use 1.5 features, he can search and replace the variable name and use -target 1.5, *but he is not forced to do that until he wants to*.
Try not to panic so easy.
You regularly drink black coffee that's a few degrees shy of boiling?
Did you lose all sensation in your mouth as a child?
No movie that features Jennifer Connelly can suck. It's just a rule.
That was my first thought too. There must be some mirrors that didn't update, or have the last known good copy of these files. I assume mirroring was shut off as soon as they discovered the breach. Some server in Russia somewhere has the known good distributions.
Okay, this kind of shit makes me want to start throwing bricks. Cracking the GNU FTP server? Is nothing sacred anymore? I feel like someone burned down a church.
They've done so much for humanity and some utter twit decides to compensate for his bad childhood by taking their server down.
*goes off to dock another point from his faith in humanity*
Maybe YOUR penis will need only one IPv6 address, but mine will require at least ten. /not funny, so no bonus.
Or, as I fervently hope is the case, IBM wants to put an end to this proprietary UNIX shit once and for all. Maybe even score a major victory on the GPL front. They think they will have to deal with these kinds of lawsuits from all kinds of people if the base issues are not dealt with in an authoritative and final manner now. Therefore, they're assembling a crushing weight of lawyers and facts to destroy SCO's case point-by-point, leaving other parties no foundation on which to build another case.
Filing for summary judgment and/or dismissal would get this case out of the courts, but what happens in six months when, say, Microsoft buys SCO and decides to attack IBM over Linux? (Hey, it could happen.)
Plus, the longer SCO talks, the more ridiculous they look and the more they open themselves to harassment suits. Let 'em dig their own grave.
Typesafe enums. That alone makes me quiver with happiness.
No worries, the hired goons just visit each of them and ask to see the Windows XP folder with the claimed serial number sticker on the back. Joe Sixpack will meekly hand it over and Joe Script-Kiddie will silently vanish into the Microsoft Dungeons.
Okay, I really hope that:
but there are some things, even in our geeky computer-loving world, that need to be done in person. If you're going to ask a girl to marry you, you do it *in person*, looking her *in the eyes*, *on your knees*, like a man. You owe both of you that much.
Anyway, best of luck to both of you and much happiness to you.
ILM is pulling 60-hour weeks (so I hear) on finishing Episode II. The new movie, if it's started shooting, needs to be in postproduction by the beginning of February. There simply isn't time.
Plus, if you were at ILM, would you rather work on Episode II or on Star Trek X? (Ideally, you'd want to do them back to back, but if you had to make a choice...)
Well, in the original script, Kirk was shot by Soran (the bad guy) with some kind of phaser weapon. I think he died after a climactic fight between Picard and Soren. Not sure why they changed it, but it wouldn't have been any better. What a stupid way to kill one of my heroes. :(
Actually he just said "port 80" -- I inferred outgoing from context. But you're right. That would be rather dumb, wouldn't it? :) Cheerfully withdrawn.
Verizon *DOES NOT BLOCK* outgoing port 25 *OR* port 80! I've been running my own mail server off the standard DSL offering, $40 a month, for almost a month now and never one hint of problems. I can send mail anywhere. I can telnet to port 25 on any Internet-accessible mail server.
And correct me if I'm wrong, but if Verizon blocks outgoing port 80, wouldn't that put a bit of a dent in most popular web browsers?
For the love of God, try to be a little accurate! There are plenty of real problems to bitch about!
Not to be too picky, but...
How about a GODDAMN SPOILER WARNING?!
sheesh.