The point was that there are plenty of purely-Canadian labels, and they're against this sort of lobbying. So you can ignore any "in the interest of Canadian artists" arguments, because it's more about the interest of global corporations, as you've pointed out.
Dude - a game by RockStar based on the bible would kick ass.
Remember when Moses slaughtered the Mideans, took their women and children prisoner, then order his men to kill all the males and non-virgin ladies, then take the young virgin ladies for themselves to do with as they pleased?
That would make a *great* video game (or movie...or book)
But the groups complaining are complaining on behalf of the end users. The reason the FCC gets involved in Nipplegate is because the end users (viewers) were exposed to something that they did not sign up for, and had a reasonable expectation of not seeing.
In... CoffeeGate?... the end users have no case at all. And the only reason the groups you listed above have a stake in this is because of groups acting on behalf of the end users.
There's no difference in the real world to the end user though. They download a file from someone who's unaffiliated with the company, then run that file.
If there is no difference at all in the "real world", why should there be any punishment? To anyone viewing the scene, the experience is exactly the same.
Where is someone's son getting XXX-Tele-Humpies-Patch.exe? If a user is required to run a patch, then they
A) Know what it's doing, and
B) Are responsible for their own actions, just as with any other content they obtain out of normal game operation.
The scene was in no way accessible without knowing *exactly* what you were doing. If a kid was able to get away with installing this patch, they were just as capable of downloading porn.
Someone could have created a mod which created that scene rather than unlocking it. For the end-user, what the hell is the difference? They're just running hot-coffee-patch.exe.
How culpable is a company for people modifying their software? If I take all of their textures and pick-and-choose-and-cut-and-paste until I have something that looks like a boobie, did the software "ship" with that boobie?
2 games: One ships with nude base models for characters, and clothing is put on top when the models are generated for display. The nude models are never shown during "normal" gameplay, but someone makes a mod to make all clothing transparent.
The other ships with a blank void where the naughty-bits are, and puts clothes on top, so you never see the blank-void-naughty-bits during gameplay. Someone makes a mod which adds in those naughty-bits.
Now of course you'll say "But game A ships with naughty-bits!". It doesn't matter - to the end user running show_naughty_bits.exe, it's the exact same experience. Out here in the real world, there's no difference. Once a game is modified from its original form, why can a company be held responsible?
True, but you don't go from neophyte to guru overnight. If you've never used a computer for anything more than Word, it doesn't matter if you program in BASIC or C, you're still producing crap.
One of the first lessons I learned in BASIC was to use arrays rather than $item1, $item2, etc.
Later I learned to reduce the amount of code by refactoring all similar code into subroutines.
Then I tried out another language, because I was told BASIC was crap (which is true), and started learning about objects.
But it certainly did nothing to hinder my learning of programming, and I'd wager I learned a lot faster without having to worry about compiling, linking, etc. Were there better languages to start out on? Probably, but not starting with the Absolute Best Starting Language isn't going to screw you for life.
If someone out there wants to be a programmer after using nothing but BASIC for 10 years, then yeah - he's screwed. But to claim that it "teaches you nothing" is simply false - it was an awesome starter language for me - the same way lego is an awesome starter tool for young engineers.
And it hasn't hindered my ability to build larger projects, because I'm always refactoring my knowledge to take in new techniques.
Basically I'm saying this - no one is a crappy programmer because of their first language. If you can't unlearn bad techniques and recognize/learn better ones, you'll be crappy your whole life, regardless of what language you started with.
==== And to get slightly back on topic, I disagree completely that PHP falls under this category - it's a niche player that did well in its niche when it was made, and is improving every year to try to keep up with competitors.
Look back to when PHP4 was written, and look at the alternatives. Web languages were just coming into their own, and PHP4 was the best of the bunch. Still crappy when compared to "real" languages - for all the reasons you describe above and more.
But most of the points you make above have been fixed with PHP5 (you say as much in the post). I think that moving into the future PHP5 is as valid a choice as Python or Ruby.
This was just for XSS protection - to make sure links from other sites (mysite.com?delete_all_my_stuff) couldn't harm the client. If the client was sending anything other than the expected referer, they were redirected to a known safe page (home page). Sure they could spoof it, but why would they want to?
The manager was brought in problem was one of the parties didn't like what Ms. Harris had to say.
"The bank manager was brought in problem was he took the cashiers side when she'd clearly cheated me"
Rules were plain before the game problem was they didn't yield the desired result. Rules were not plain before the game. Answer this - if a machine malfunctions and counts zero for candidate X, but provides paper ballots that show 123 votes for candidate X, which do you use? The rules can't *possibly* be plain, because so many things can go wrong, and you have to use a little common sense.
Good points - I've worked mostly with internal systems though, and never had any complaints from people who have referers turned off. It's not a common practice. Still - I'll use the method you describe in the future.
It may not have been the "best practice", but it did keep my users safe, which is all I care about.
God you're a moron! (it just seems you begin every post with an invective, thought I'd try it on, see how it feels)
Anyway, on to the answers!
Which do you think is more likely to cheat you a cashier or an ATM Cashier. But if there's a question about the accuracy of a transaction, you bring in the (human) manager either way.
Do you decide the rules of a game before you start playing or after its over ? Before. But in this case the rules were none too clear. If a chad is dimpled, is that a vote, or not? It's clear who the voter intended to cast their vote for, but the chad is dimpled!
This was a unique situation in US history - a single state determining the presidency by a small fraction of a percent of the voting population. If it was for the next American Idol, I'd say let the SC decide and be done with it, but for the Presidency of the United States of America? The whole thing was determined by political maneuvering and lawsuits, rather than finding out who actually got the most votes.
Sure I'm not. I've done it before and I'll do it again. But you're offering me nothing but innuendo.
Pennies? Get together a few hundred people. Divide them into teams (let's call them D's and R's). Assign one D and R to each group. Have each group keep counting their pile until they both agree on the number of pennies.
Sum up the total from all groups. That's the number of pennies.
At least that way, both teams agree on the total. Which I think is the main problem - there was no willingness shown to come up with a solution that could at least be agreed upon. The result was pushed through, and left a lot of people unsatisfied.
Slashdot Mirror
Probably the same motivation that faults Communism for corruption and incompetence of politicians.
The point was that there are plenty of purely-Canadian labels, and they're against this sort of lobbying. So you can ignore any "in the interest of Canadian artists" arguments, because it's more about the interest of global corporations, as you've pointed out.
Dude - a game by RockStar based on the bible would kick ass.
Remember when Moses slaughtered the Mideans, took their women and children prisoner, then order his men to kill all the males and non-virgin ladies, then take the young virgin ladies for themselves to do with as they pleased?
That would make a *great* video game (or movie...or book)
But the groups complaining are complaining on behalf of the end users. The reason the FCC gets involved in Nipplegate is because the end users (viewers) were exposed to something that they did not sign up for, and had a reasonable expectation of not seeing.
... CoffeeGate? ... the end users have no case at all. And the only reason the groups you listed above have a stake in this is because of groups acting on behalf of the end users.
In
There's no difference in the real world to the end user though. They download a file from someone who's unaffiliated with the company, then run that file.
If there is no difference at all in the "real world", why should there be any punishment? To anyone viewing the scene, the experience is exactly the same.
Where is someone's son getting XXX-Tele-Humpies-Patch.exe? If a user is required to run a patch, then they
A) Know what it's doing, and
B) Are responsible for their own actions, just as with any other content they obtain out of normal game operation.
The scene was in no way accessible without knowing *exactly* what you were doing. If a kid was able to get away with installing this patch, they were just as capable of downloading porn.
Touché
Someone could have created a mod which created that scene rather than unlocking it. For the end-user, what the hell is the difference? They're just running hot-coffee-patch.exe.
How culpable is a company for people modifying their software? If I take all of their textures and pick-and-choose-and-cut-and-paste until I have something that looks like a boobie, did the software "ship" with that boobie?
Okay - please - explain this to me:
2 games:
One ships with nude base models for characters, and clothing is put on top when the models are generated for display. The nude models are never shown during "normal" gameplay, but someone makes a mod to make all clothing transparent.
The other ships with a blank void where the naughty-bits are, and puts clothes on top, so you never see the blank-void-naughty-bits during gameplay. Someone makes a mod which adds in those naughty-bits.
Now of course you'll say "But game A ships with naughty-bits!". It doesn't matter - to the end user running show_naughty_bits.exe, it's the exact same experience. Out here in the real world, there's no difference. Once a game is modified from its original form, why can a company be held responsible?
It didn't happen with the abacus, it didn't happen with the slide rule, and it didn't happen with calculators. I doubt it'll happen now.
As long as we can follow the trail of calculations from beginning to end, there's still the ability to understand what's happening.
source?
Actually, it was shorthand for "the revenue SL takes in in a quarter"
There's a good reason for that. Take a look at just about any code, and you can see a few ways to improve it. Hence, you're "better" than the coder.
Nevermind that the code you actually produce is 10x worse - if you can see where it can be improved, you must be better.
True, but you don't go from neophyte to guru overnight. If you've never used a computer for anything more than Word, it doesn't matter if you program in BASIC or C, you're still producing crap.
One of the first lessons I learned in BASIC was to use arrays rather than $item1, $item2, etc.
Later I learned to reduce the amount of code by refactoring all similar code into subroutines.
Then I tried out another language, because I was told BASIC was crap (which is true), and started learning about objects.
But it certainly did nothing to hinder my learning of programming, and I'd wager I learned a lot faster without having to worry about compiling, linking, etc. Were there better languages to start out on? Probably, but not starting with the Absolute Best Starting Language isn't going to screw you for life.
If someone out there wants to be a programmer after using nothing but BASIC for 10 years, then yeah - he's screwed. But to claim that it "teaches you nothing" is simply false - it was an awesome starter language for me - the same way lego is an awesome starter tool for young engineers.
And it hasn't hindered my ability to build larger projects, because I'm always refactoring my knowledge to take in new techniques.
Basically I'm saying this - no one is a crappy programmer because of their first language. If you can't unlearn bad techniques and recognize/learn better ones, you'll be crappy your whole life, regardless of what language you started with.
====
And to get slightly back on topic, I disagree completely that PHP falls under this category - it's a niche player that did well in its niche when it was made, and is improving every year to try to keep up with competitors.
Look back to when PHP4 was written, and look at the alternatives. Web languages were just coming into their own, and PHP4 was the best of the bunch. Still crappy when compared to "real" languages - for all the reasons you describe above and more.
But most of the points you make above have been fixed with PHP5 (you say as much in the post). I think that moving into the future PHP5 is as valid a choice as Python or Ruby.
Good. Hate those guys.
This was just for XSS protection - to make sure links from other sites (mysite.com?delete_all_my_stuff) couldn't harm the client. If the client was sending anything other than the expected referer, they were redirected to a known safe page (home page). Sure they could spoof it, but why would they want to?
Look, I'm sorry - I know this isn't really part of the game, but I just have to know.
Troll or stupid?
You're welcome, thank you for confirming mine.
The manager was brought in problem was one of the parties didn't like what Ms. Harris had to say.
"The bank manager was brought in problem was he took the cashiers side when she'd clearly cheated me"
Rules were plain before the game problem was they didn't yield the desired result.
Rules were not plain before the game. Answer this - if a machine malfunctions and counts zero for candidate X, but provides paper ballots that show 123 votes for candidate X, which do you use? The rules can't *possibly* be plain, because so many things can go wrong, and you have to use a little common sense.
Good points - I've worked mostly with internal systems though, and never had any complaints from people who have referers turned off. It's not a common practice. Still - I'll use the method you describe in the future.
It may not have been the "best practice", but it did keep my users safe, which is all I care about.
More importantly, Referer can be used to make sure users aren't coming from *other* sites, to prevent cross-site scripting. For example:
e te_all_my_stuff
http://www.your-site.com/do_action.php?action=del
Check the referer. It's not your-site.com? Don't delete all my stuff.
God you're a moron! (it just seems you begin every post with an invective, thought I'd try it on, see how it feels)
Anyway, on to the answers!
Which do you think is more likely to cheat you a cashier or an ATM
Cashier. But if there's a question about the accuracy of a transaction, you bring in the (human) manager either way.
Do you decide the rules of a game before you start playing or after its over ?
Before. But in this case the rules were none too clear. If a chad is dimpled, is that a vote, or not? It's clear who the voter intended to cast their vote for, but the chad is dimpled!
This was a unique situation in US history - a single state determining the presidency by a small fraction of a percent of the voting population. If it was for the next American Idol, I'd say let the SC decide and be done with it, but for the Presidency of the United States of America? The whole thing was determined by political maneuvering and lawsuits, rather than finding out who actually got the most votes.
Sure youre not kid.
Sure I'm not. I've done it before and I'll do it again. But you're offering me nothing but innuendo.
Pennies? Get together a few hundred people. Divide them into teams (let's call them D's and R's). Assign one D and R to each group. Have each group keep counting their pile until they both agree on the number of pennies.
Sum up the total from all groups. That's the number of pennies.
At least that way, both teams agree on the total. Which I think is the main problem - there was no willingness shown to come up with a solution that could at least be agreed upon. The result was pushed through, and left a lot of people unsatisfied.