*Shrug* they both do, actually. It's because you have to declare hashes or arrays to make that work properly under strict. I didn't think it was fair to have strict on when comparing it to php, because php has no strict.
Beat you by 6 characters on that second one. And if I'm not allowed to use references, you're not allowed to use strings. Perl is designed with references in mind.
This is why you should use a bad-password delay on your system. It doesn't matter how many passwords some fast computer can try a second if the system enforces a 2-second delay after each attempt.
>Bugs are inevitable, but its not the user's responsibility to take the heat >for the programmer's screw ups.
The user is not taking the heat for the programmer's screwups- the user is taking the heat for EXPLOITING the screwup- an important difference.
>That'd be like you going to jail for taking Advil yesterday because the drug >was made illegal today.
I'm sorry, but that analogy makes no sense. This is not retroactive enforcement of a law, this is a bunch of users violating the terms of their agreement and being nailed for it. They knew the outcome wouldn't be pleasant if they were caught
>As far as I'm concerned, the SB players who exploited the bug were well >within their right to do so.
Don't mention their "right" to do so- it doesn't support you at all. They had the right to exploit it, and ubisoft had the right to ban them. End of story.
>Deadline or not, software should be released functional not early. I'll >gladly wait for a game to be released an extra year if it is guaranteed to be >quality.
This shows that you are very naive about how the whole process works. You (and even I, sometimes) would be willing to wait, but the game's producer will _not_. If developers had their way on this, you'd see a release schedule like Blizzard's. They produce their own games, so they can wait as long as they want to release them. This is why Blizzard games are always delayed, and why their initial releases are almost always more polished than most other games. However, most producers are not so forgiving, and eventually the game reaches a point where the publishers just say "ship it- you can fix it with the first patch." No coder wants an unfinished product of theirs to go out- just look at Carmack's reaction to the leaked Doom3 pre-alpha.
>Developers never seem to take the time to test for this crap. The >very fact that a bug existed in their public release so large that any old >user could wiggle his way into "god mode" is shameful.
In fact, developers don't usually do serious testing at all- instead, QA does it. Then they send this report back to the developers. The QA team is usually made up partially of QA from the developers' company, and partially from the producer's company. This is not always the case, but it is often enough. As I said above, the producer makes the final call. They paid for it, they call the shots.
>If I were in charge over there, I'd have a good laugh with it, fix it, revert >the server, and move on. Treating this retarded exploitation of an in-game bug >like some kind of evil crime is silly, and so is anyone who actually takes crap >like that so seriously.
Murder is an evil crime. Cheating is not. Murder can get you the death penalty. Cheating can get you banned from the game. If they just had a "good laugh" about this, they would have shown that they don't mind cheating that much. Instead, they've shown that they will not tolerate it, and in the future cheaters will have to weigh this with their need to cheat.
Have you ever written a large-scale game? Or for that matter, any sort of large software program with many many users? Probably not, though I see your subspace zone- after the fall of VIE, I always preferred Trench Wars.:)
Sure, they coded the bug in, so of course it's their fault, right? And you, on the other hand, are perfect? You never make errors? I'll help you a bit- it's not "looses", it's "loses". You made a grammatical error in 6-sentence comment. They made an error in what is probably a 500K+ line program.
I am by no means defending the declining quality of newly-released games, but at the same time I am willing to cut them slack- I know what it's like. Tight deadlines do not do good things for code quality. At the same time, MMORPGs are pretty close to a worst-case game scenario. Millions of users, very large world, and a dev team nowhere near the size of the user base. Cheating results in very real advantages over other players- instead of a good record (ie, cheating in CS), cheating MMORPG players can even go as far as selling their ill-gotten gains for real money.
As for the benefits of the mass banning- think on this. Some people do not cheat. How do you think they feel when they see people cheat? Pretty bad, I'd think. That's the sort of situation that one would not pay to be in. So you lose some non-cheaters due to cheaters. So, you lose the kind of people you'd like to play with due to the people who have no respect for those around them. Does that sound good to you?
1) I actually prefer it that way, because otherwise you end up with layers upon layers of compat. when you really don't need it. This way, I only get it if I actually need to run libc5 programs. Avoiding cruft is good.
3) Linux does not just run on 64-bit systems. So you probably won't see that. Things that need to be 64-bit will be, otherwise they won't be. You actually contradict yourself on this one- adding 64-bit code where it isn't necessary is a good way of breaking backwards-compatibility. Yes, I know, it can be worked around (Solaris obviously did), but that's where the compatibility libraries come in. See #1
5) You provided a description of the filesystems, but you didn't actually say why ReiserFS deserves "beta" status. I perfectly agree with you opinion of XFS (I think it hates me). But neither Ext3 nor ReiserFS has ever given me any trouble, and I don't hear people actually having problems with ReiserFS anymore. Sure, at one time there were a few problems, but every recent case of someone bashing ReiserFS I've seen was hearsay. I don't buy it. The only thing that I don't like about ReiserFS is the lack of ACL support (they come in handy). That'll be in ReiserFS4, which I can't wait for.
1. Distro-dependent. Here's how you do it with Gentoo: emerge sys-devel/gcc-compat sys-libs/lib-compat and you'll get support for everything back to libc5. Thus binary compatibility. You will no doubt point out the irony of providing an example with a somewhat bsd-like linux distro. I respond: And?
2. Being worked on. Read linux-kernel. It runs on 32-proc systems, and it (apparently) runs rather well.
3. People have been working on x86-64 in linux for a long time. I went to a presentation at linuxworld, august 2001, and SuSE had 64-bit code running back then. It's just gotten better since then, especially since Linus likes it. Linuxworld 2002 saw me playing with the Gimp on an Opteron. Worked very nice:)
4. Dunno much about this. I can admit this.
5. This point shows a complete lack of research. Linux has journaling filesystems coming out of its ears. Reiserfs, ext3, jfs, xfs, etc. Also, "it's been good enough for years" is never a good argument for anything. Solaris is "good enough" in your opinion, so should Sun stop improving it?
>> Oh, and by the way, ctl-alt-+ and ctl-alt-- changes your resolutions in X on-the-fly,
> As much as I love Linux/X11, I find the method you mentioned as less than desirable. Yes, it changes the resolution. It also leaves me with a virtual desktop size of the default resolution. Thus, to see all of the desktop at once is not possible, requiring me to mouse to the edges and have the "view" scroll around.
Upgrade to X 4.3 (or wait until your distro does it for you): "xrandr -s 1600x1200" switches the rez. Not just zooming like ctrl-alt-+ does. Try it.
> What is it that causes these kinds of conflicts and mistrust?
Human nature. Contrary to popular belief, os/fs coders are human. Though some seem to have magical time-stretching powers that allow them to do more than a human should be able to in one day.
There are inflated egos among os/fs coders, because, once again, they are human. There are many inflated egos that don't belong to coders as well.
The reason this seems to crop up connected os/fs projects is if/when this happens at a company, _it doesn't get out_. The company doesn't want to lose image points, so conflicts stay internal. On the other hand, how do you keep an os/fs conflict internal? Have the developers talk mind to mind? They talk on public lists most of the time.
And sure, we're crackpots. Some of us prefer to fix something we don't like in software we use. Fixing something you didn't write? Horrors! Putting your heart and time into a project that doesn't make you any money! CRACKPOTS! She's a witch! BURN HER!
Why would one pay for Staroffice when Openoffice is free in all senses and more up to date? Use a bit of logic- the only reason to pay for Staroffice would be to get the support that Sun provides. If you don't need the support, you can use Openoffice. This also applies to your distro iso argument. Posting serial numbers is inexcusable, but don't lump logical choices in with your rant. You don't pay for software you don't need.
>So you define randomness in terms of probability? A minimum requirement for a completely random selection is that the set of objects chosen from have an equal probability of being chosen. Otherwise, it is not fully random (ignoring the fact that very little is fully random in real life).
>Define what probability is. Do your best not to invoke the definition of random. Doing your homework for you: dictionary.com: 3a. The likelihood that a given event will occur. 3b. Statistics. A number expressing the likelihood that a specific event will occur, expressed as the ratio of the number of actual occurrences to the number of possible occurrences.
Oh, and while we're at it, let's look up random, too! 2. Mathematics & Statistics. Of or relating to a type of circumstance or event that is described by a probability distribution. 3. Of or relating to an event in which all outcomes are equally likely, as in the testing of a blood sample for the presence of a substance.
Equal probability. Every dictionary i could get my (literal or figurative) hands on all define random in terms of probability. So, now I fire a question back. You don't define random in terms of probability?
Er, no. If you select the numbers serially, you know EXACTLY what the next number is. If you select 0, selecting serially, then the next number is 1. That's not equal probability, that's certainty. You can't just think of the global case when doing probability.
You could do what i do- since i get fairly standard spam messages (when i do get them), i just wrote a quick perl script for gaim. Reads from a list of regexps, blocks the message if they match. That simple. (and couldn't be done with the ugly bloated client aol has). Catch 22, yes, but you can do much more with perl than just block spam:)
The storyline for those is already written. Go check out the Rogue Squadron series. Start here
Re:I know, it's a feature.
on
Pet Bugs?
·
· Score: 4, Informative
I've had that problem before, but it's not what you think (i think). Do you use zsh? Some shells, including zsh, protect their prompt. So if you print a single line w/o a \n, the prompt overwrites it, and you never see it. I think that bash by default will just print the prompt after whatever it was you printed. Try piping it to less or something, and you'll see it IS actually there:)
I remember when i read the "trilogy" for the first time.. sigh.. have fun in infinity!
1 AREA: Infinite
The Hitchhiker's Guide to the Galaxy offers this definition of the word "Infinite."
Infinite: Bigger that the biggest thing ever and then some. Much bigger than that in fact, really amazingly immense, a totally stunning size, real "wow, that's big," time. Infinity is just so big that, by comparison, bigness itself looks really titchy. Gigantic multiplied by colossal multiplied by staggeringly huge is the sort of concept we're trying to get across here."
This is what i've been saying all along about Napster. MP3s are great, and i have a lot of them, but they will never replace the real albums. I have 160 CDs, which means i've paid (doing a bit of averaging) about $2000 for cds... oh, did i mention, that before i began using Napster, i had about 12?
Sure there are abuse cases.. anyone can abuse anything. But this doesn't mean that EVERYONE freeloads! Down with Generalizations!:)
This dude checks out the movies and rates them based on science.. check it out.. some of those asteroid movies are really bad...
http://www.badastronomy.com/bad/movies/index.htm l
Hey, I'm doing a research project on this very sort of thing! Actually, it's mostly on the RIAA itself and how it's hypocritical and all that other nifty stuff. If anyone knows any sites that have good (factual, un-flameage) RIAA-bashing stuff, I'd greatly appreciate it:)
Anyway, my view is that the RIAA is a Bad Thing and should be broken up to some extent. I mean, look at the cd prices in, say, Hong Kong. They're really low. Do you know why? Because they have a huge black market! The local vendors (would be Tower/Wherehouse/Sam Goody in the US) are forced to lower their prices to compete with the black market, and people get less screwed over! (It costs pennies to make cds, more to do advertising and stuff, but it does NOT account for the $18-20 cds some places sell). Anyway, that's my view. Respond! I commandith thee!
My house's network is pretty nifty. We have (almost.. you don't need ethernet on the pot ^_^) every room in the house wired for cable tv, phone, and ethernet. All wires come out at a central location in our garage, where the router, modem, and various other thingies are. We had it all put in when our house was remodeled. Having had to deal with this put in, i have some advice:
1) Don't let the electrician (or whatever specialist for each type of wire) leave until you've tested each room! It took us a week to get the guy to come back after we found out that one room (mine! grrr) had a dead link.
2) Keep it neat
3) (Quite possibly the most important, although obvious for MOST people) Color-code everything! Nothing more irritating than being forced to test every cable to figure out where it goes (all of our ethernet lines weren't marked..had to plug the computers in one by one and see which lights on the hub lit up.. don't laugh!)
4) If you have the skill, set up an old computer as a router rather than using a storebought one, unless you plan on paying for a cisco one. We bought a linksys, and it dropped the connection every 3 days and had to be reset, from the shipping version of the firmware to the present one. So i converted a 100mhz p1, and everything became happy again:)
hehe, just wanted to point out that my brother is on team 254, one of the teams from the 2nd place alliance:) His team can be found here He was the main driver for the team, and also one of the VERY few freshman to have that honor.
Slashdot Mirror
Also, for landing on Mars, NASA takes some precautions against contamination. This page talks a little bit about the bio-barrier around Phoenix's arm: http://www.popularmechanics.com/science/air_space/4265740.html?page=7&series=35
*Shrug* they both do, actually. It's because you have to declare hashes or arrays to make that work properly under strict. I didn't think it was fair to have strict on when comparing it to php, because php has no strict.
$y[0][0][0] = 0;
$x{a}{b}{c} = 'd';
Beat you by 6 characters on that second one. And if I'm not allowed to use references, you're not allowed to use strings. Perl is designed with references in mind.
This is why you should use a bad-password delay on your system. It doesn't matter how many passwords some fast computer can try a second if the system enforces a 2-second delay after each attempt.
>Bugs are inevitable, but its not the user's responsibility to take the heat
>for the programmer's screw ups.
The user is not taking the heat for the programmer's screwups- the user is
taking the heat for EXPLOITING the screwup- an important difference.
>That'd be like you going to jail for taking Advil yesterday because the drug
>was made illegal today.
I'm sorry, but that analogy makes no sense. This is not retroactive
enforcement of a law, this is a bunch of users violating the terms of their
agreement and being nailed for it. They knew the outcome wouldn't be pleasant
if they were caught
>As far as I'm concerned, the SB players who exploited the bug were well
>within their right to do so.
Don't mention their "right" to do so- it doesn't support you at all. They had
the right to exploit it, and ubisoft had the right to ban them. End of story.
>Deadline or not, software should be released functional not early. I'll
>gladly wait for a game to be released an extra year if it is guaranteed to be
>quality.
This shows that you are very naive about how the whole process works. You (and
even I, sometimes) would be willing to wait, but the game's producer will
_not_. If developers had their way on this, you'd see a release schedule like
Blizzard's. They produce their own games, so they can wait as long as they
want to release them. This is why Blizzard games are always delayed, and why
their initial releases are almost always more polished than most other games.
However, most producers are not so forgiving, and eventually the game reaches a
point where the publishers just say "ship it- you can fix it with the first
patch." No coder wants an unfinished product of theirs to go out- just look at
Carmack's reaction to the leaked Doom3 pre-alpha.
>Developers never seem to take the time to test for this crap. The
>very fact that a bug existed in their public release so large that any old
>user could wiggle his way into "god mode" is shameful.
In fact, developers don't usually do serious testing at all- instead, QA does
it. Then they send this report back to the developers. The QA team is usually
made up partially of QA from the developers' company, and partially from the
producer's company. This is not always the case, but it is often enough. As I
said above, the producer makes the final call. They paid for it, they call the
shots.
>If I were in charge over there, I'd have a good laugh with it, fix it, revert
>the server, and move on. Treating this retarded exploitation of an in-game bug
>like some kind of evil crime is silly, and so is anyone who actually takes crap
>like that so seriously.
Murder is an evil crime. Cheating is not. Murder can get you the death penalty.
Cheating can get you banned from the game. If they just had a "good laugh"
about this, they would have shown that they don't mind cheating that much.
Instead, they've shown that they will not tolerate it, and in the future
cheaters will have to weigh this with their need to cheat.
Have you ever written a large-scale game? Or for that matter, any sort of large software program with many many users? Probably not, though I see your subspace zone- after the fall of VIE, I always preferred Trench Wars. :)
Sure, they coded the bug in, so of course it's their fault, right? And you, on the other hand, are perfect? You never make errors? I'll help you a bit- it's not "looses", it's "loses". You made a grammatical error in 6-sentence comment. They made an error in what is probably a 500K+ line program.
I am by no means defending the declining quality of newly-released games, but at the same time I am willing to cut them slack- I know what it's like. Tight deadlines do not do good things for code quality. At the same time, MMORPGs are pretty close to a worst-case game scenario. Millions of users, very large world, and a dev team nowhere near the size of the user base. Cheating results in very real advantages over other players- instead of a good record (ie, cheating in CS), cheating MMORPG players can even go as far as selling their ill-gotten gains for real money.
As for the benefits of the mass banning- think on this. Some people do not cheat. How do you think they feel when they see people cheat? Pretty bad, I'd think. That's the sort of situation that one would not pay to be in. So you lose some non-cheaters due to cheaters. So, you lose the kind of people you'd like to play with due to the people who have no respect for those around them. Does that sound good to you?
1) I actually prefer it that way, because otherwise you end up with layers upon layers of compat. when you really don't need it. This way, I only get it if I actually need to run libc5 programs. Avoiding cruft is good.
3) Linux does not just run on 64-bit systems. So you probably won't see that. Things that need to be 64-bit will be, otherwise they won't be. You actually contradict yourself on this one- adding 64-bit code where it isn't necessary is a good way of breaking backwards-compatibility. Yes, I know, it can be worked around (Solaris obviously did), but that's where the compatibility libraries come in. See #1
5) You provided a description of the filesystems, but you didn't actually say why ReiserFS deserves "beta" status. I perfectly agree with you opinion of XFS (I think it hates me). But neither Ext3 nor ReiserFS has ever given me any trouble, and I don't hear people actually having problems with ReiserFS anymore. Sure, at one time there were a few problems, but every recent case of someone bashing ReiserFS I've seen was hearsay. I don't buy it. The only thing that I don't like about ReiserFS is the lack of ACL support (they come in handy). That'll be in ReiserFS4, which I can't wait for.
1. Distro-dependent. Here's how you do it with Gentoo:
:)
emerge sys-devel/gcc-compat sys-libs/lib-compat
and you'll get support for everything back to libc5. Thus binary compatibility. You will no doubt point out the irony of providing an example with a somewhat bsd-like linux distro. I respond: And?
2. Being worked on. Read linux-kernel. It runs on 32-proc systems, and it (apparently) runs rather well.
3. People have been working on x86-64 in linux for a long time. I went to a presentation at linuxworld, august 2001, and SuSE had 64-bit code running back then. It's just gotten better since then, especially since Linus likes it. Linuxworld 2002 saw me playing with the Gimp on an Opteron. Worked very nice
4. Dunno much about this. I can admit this.
5. This point shows a complete lack of research. Linux has journaling filesystems coming out of its ears. Reiserfs, ext3, jfs, xfs, etc. Also, "it's been good enough for years" is never a good argument for anything. Solaris is "good enough" in your opinion, so should Sun stop improving it?
6,7 See 4.
>> Oh, and by the way, ctl-alt-+ and ctl-alt-- changes your resolutions in X on-the-fly,
:
> As much as I love Linux/X11, I find the method you mentioned as less than desirable. Yes, it changes the resolution. It also leaves me with a virtual desktop size of the default resolution. Thus, to see all of the desktop at once is not possible, requiring me to mouse to the edges and have the "view" scroll around.
Upgrade to X 4.3 (or wait until your distro does it for you)
"xrandr -s 1600x1200" switches the rez. Not just zooming like ctrl-alt-+ does. Try it.
> What is it that causes these kinds of conflicts and mistrust?
Human nature. Contrary to popular belief, os/fs coders are human. Though some seem to have magical time-stretching powers that allow them to do more than a human should be able to in one day.
There are inflated egos among os/fs coders, because, once again, they are human. There are many inflated egos that don't belong to coders as well.
The reason this seems to crop up connected os/fs projects is if/when this happens at a company, _it doesn't get out_. The company doesn't want to lose image points, so conflicts stay internal. On the other hand, how do you keep an os/fs conflict internal? Have the developers talk mind to mind? They talk on public lists most of the time.
And sure, we're crackpots. Some of us prefer to fix something we don't like in software we use. Fixing something you didn't write? Horrors! Putting your heart and time into a project that doesn't make you any money! CRACKPOTS! She's a witch! BURN HER!
Why would one pay for Staroffice when Openoffice is free in all senses and more up to date? Use a bit of logic- the only reason to pay for Staroffice would be to get the support that Sun provides. If you don't need the support, you can use Openoffice. This also applies to your distro iso argument. Posting serial numbers is inexcusable, but don't lump logical choices in with your rant. You don't pay for software you don't need.
I'm curious. Could you possibly find a link? I googled for it, but I'm not quite sure what to look for.
>So you define randomness in terms of probability?
A minimum requirement for a completely random selection is that the set of objects chosen from have an equal probability of being chosen. Otherwise, it is not fully random (ignoring the fact that very little is fully random in real life).
>Define what probability is. Do your best not to invoke the definition of random.
Doing your homework for you:
dictionary.com:
3a. The likelihood that a given event will occur.
3b. Statistics. A number expressing the likelihood that a specific event will occur, expressed as the ratio of the number of actual occurrences to the number of possible occurrences.
Oh, and while we're at it, let's look up random, too!
2. Mathematics & Statistics. Of or relating to a type of circumstance or event that is described by a probability distribution.
3. Of or relating to an event in which all outcomes are equally likely, as in the testing of a blood sample for the presence of a substance.
Equal probability. Every dictionary i could get my (literal or figurative) hands on all define random in terms of probability. So, now I fire a question back. You don't define random in terms of probability?
Er, no. If you select the numbers serially, you know EXACTLY what the next number is. If you select 0, selecting serially, then the next number is 1. That's not equal probability, that's certainty. You can't just think of the global case when doing probability.
You could do what i do- since i get fairly standard spam messages (when i do get them), i just wrote a quick perl script for gaim. Reads from a list of regexps, blocks the message if they match. That simple. (and couldn't be done with the ugly bloated client aol has). Catch 22, yes, but you can do much more with perl than just block spam :)
The storyline for those is already written. Go check out the Rogue Squadron series. Start here
I've had that problem before, but it's not what you think (i think). Do you use zsh? Some shells, including zsh, protect their prompt. So if you print a single line w/o a \n, the prompt overwrites it, and you never see it. I think that bash by default will just print the prompt after whatever it was you printed. Try piping it to less or something, and you'll see it IS actually there :)
I use linux with mplayer, and i had no trouble playing the wma :)
Thanks :) i was getting tired of "Click continue; wait; click 'ok' on timeout; repeat"
:)
heh
I remember when i read the "trilogy" for the first time.. sigh.. have fun in infinity!
1 AREA: Infinite
The Hitchhiker's Guide to the Galaxy offers this definition of the word "Infinite."
Infinite: Bigger that the biggest thing ever and then some. Much bigger than that in fact, really amazingly immense, a totally stunning size, real "wow, that's big," time. Infinity is just so big that, by comparison, bigness itself looks really titchy. Gigantic multiplied by colossal multiplied by staggeringly huge is the sort of concept we're trying to get across here."
This is what i've been saying all along about Napster. MP3s are great, and i have a lot of them, but they will never replace the real albums. I have 160 CDs, which means i've paid (doing a bit of averaging) about $2000 for cds... oh, did i mention, that before i began using Napster, i had about 12?
:)
Sure there are abuse cases.. anyone can abuse anything. But this doesn't mean that EVERYONE freeloads! Down with Generalizations!
This dude checks out the movies and rates them based on science.. check it out.. some of those asteroid movies are really bad...m l
http://www.badastronomy.com/bad/movies/index.ht
Hey, I'm doing a research project on this very sort of thing! Actually, it's mostly on the RIAA itself and how it's hypocritical and all that other nifty stuff. If anyone knows any sites that have good (factual, un-flameage) RIAA-bashing stuff, I'd greatly appreciate it :)
Anyway, my view is that the RIAA is a Bad Thing and should be broken up to some extent. I mean, look at the cd prices in, say, Hong Kong. They're really low. Do you know why? Because they have a huge black market! The local vendors (would be Tower/Wherehouse/Sam Goody in the US) are forced to lower their prices to compete with the black market, and people get less screwed over! (It costs pennies to make cds, more to do advertising and stuff, but it does NOT account for the $18-20 cds some places sell). Anyway, that's my view. Respond! I commandith thee!
1) Don't let the electrician (or whatever specialist for each type of wire) leave until you've tested each room! It took us a week to get the guy to come back after we found out that one room (mine! grrr) had a dead link.
2) Keep it neat
3) (Quite possibly the most important, although obvious for MOST people) Color-code everything! Nothing more irritating than being forced to test every cable to figure out where it goes (all of our ethernet lines weren't marked..had to plug the computers in one by one and see which lights on the hub lit up.. don't laugh!)
4) If you have the skill, set up an old computer as a router rather than using a storebought one, unless you plan on paying for a cisco one. We bought a linksys, and it dropped the connection every 3 days and had to be reset, from the shipping version of the firmware to the present one. So i converted a 100mhz p1, and everything became happy again :)
hehe, just wanted to point out that my brother is on team 254, one of the teams from the 2nd place alliance :) His team can be found here He was the main driver for the team, and also one of the VERY few freshman to have that honor.