Your other replier is wrong. There is another golf game, Super Swing Golf. I've read differing opinions on it, but haven't played it. It is, however, even more cutesy than Wii Sports golf.
They jacked the price up completely for their own benefit... but with no real reason!
I guess you must be very young, and have never taken an economics course. Although I'm sure some, or even most, of the people at Nintendo actually like making games, their purpose as a company is to make money. They aren't doing it just to make you happy. The reason, that you seem to think is missing, is to make money.
But like every company, they're going in for the whole "We'll charge more because we can. what's to stop us? people will still pay it."
This is how supply and demand works. The Wii is not necessary for survival. Therefore, if "people will still pay", those people must think the price is justified. Why should Nintendo lower the price if people will pay a higher one? They aren't running a gaming charity. They want to make money. And, as you said, people will still pay, because they think the price is worth it. Nintendo makes money, people still get their consoles. It's a win-win.
I've been using PowerShell for a couple months, and it's definitely better than cmd.exe. However, it's really built more like an interactive scripting environment, with shell features left as an afterthought.
Only the most basic redirection is implemented. Basically you can use "> file", "2> file", and "2>&1". That's it. You can't create arbitrary fd's and dup them. It's like they didn't realize that the '1' representing stdout and '2' representing stderr actually mean something more general. Oh, and no input redirection. Trying to do: somecommand < file gives you this error: The redirection operator '<' is not supported yet. At line:1 char:14 + somecommand < <<<< test.txt
Although you can technically use "2> file" to redirect errors, it's actually a big pain. Say your program outputs to stderr for various warnings, and you want to capture those. Well because everything is an object, each error line is converted to an ErrorRecord object, which is then serialized. Unfortunately, the serialization of an ErrorRecord includes a bunch of other clutter. Here's an example of one error line: > perl -e 'warn qq[Something bad happened!\n]' 2> out.err > cat out.err perl.exe : Something bad happened! At line:1 char:5 + perl <<<< -e 'warn qq[Something bad happened!\n]' 2> out.err Three lines for every error, with a bunch of clutter to make it hard to read. In order to get succinct log files, I had to write my own ErrorRecord converter to get back to the one line I want.
Command argument parsing is broken. The parser will split arguments that look like "-x12.34". So if you try to pass a switch with a floating point number as part of it, the program actually receives two separate arguments: "-x12" and ".34". You have to quote the entire thing to get it passed as one argument.
One major annoyance with cmd.exe that has not been completely fixed is the quoting inconsistencies. Nested quotes don't seem to work right. In most shells, single quotes prevent any interpretation of the string, which is mostly true in PowerShell. So when writing a quick Perl one-liner, I use single quotes to make sure any Perl variables aren't interpreted by the shell. perl -e '$k = "hello"; print $k' That seems to work, and prints 'hello'. However, try adding a newline: perl -e '$k = "hello\n"; print $k' Now Perl gives me a syntax error regarding the backslash, which leads me to believe the shell is interpreting the string before handing it to Perl. In this case, I can work around it because Perl has its own quoting operators: perl -e '$k = qq[hello\n]; print $k' But how would you pass a string like this to some other program where you needed the quotes? I couldn't figure it out.
As a scripting environment, it's pretty nice. And like I said, it is better than cmd.exe. However, basic shell functionality is semi-broken in many ways, because of the focus on Being Innovative With Everything As An Object.
PS. Don't forget that the escape character is ` (backquote), and not \ (backslash) like in every other shell/language.
Here's some insight for you: if the sound-generating toys annoy you so much, don't buy them. I doubt your two year old is buying his own toys. Get him some good old wood blocks or giant-sized legos. Not only will you get some quiet, it'll help him develop imagination instead of attention deficit disorder.
You don't need a Dvorak keyboard. Most operating systems (including Windows and Linux) let you switch the key layout in software. Sure, the keys are labeled wrong at that point, but how often do you look at your fingers while typing?
The Vim thing isn't bad. Just remap some of the keys and it's fine. Although cut/copy/paste in most apps does get more annoying.
The biggest reason I've heard for switching is not quickness. It's finger-health. Since the keys are laid out with a regard for typing English, it's much easier on your fingers. Many words can be typed without leaving the home row.
Your sig: BSD code is free code to be used in software. GPL code is code to be used in free software.
Although it makes the structure nice, using "free code" for the BSD case muddles the meaning. It would be more accurate to say: BSD code is code to be freely used in software. GPL code is code to be used in free software.
In Linux, you *have* to have a Start menu (or some analog).
I don't have one. I have a couple shortcut icons for commonly used programs and that's it. Uncommonly used programs are started from a command line widget next to my clock.
Linux advocates love to deride OS X... Yet constantly, the Linux crowd comes up with nonsensical things...
This type of comment is worthless. The "Linux crowd" is not the Borg. It's made up of people with different tastes and interests. Some of them don't like aspects of OS X, and some of them do. It's not a contradiction.
Why don't you just use your pager and drag the small picture of the app to another desktop? Doesn't everyone using virtual desktops use a graphical pager?
The whole cube thing seems whizz-bang, but not particularly productive.
I haven't played either of them yet, but Excite Truck and Super Monkey Ball both use the controller tilt, as opposed to just detecting a random motion. In Excite Truck, you use the remote like a steering wheel to steer the truck, and tilting it forward or backward while in the air changes the tilt of the truck, which affects your landing. In Super Monkey Ball, the tilt of the remote changes the tilt of the floor to move your ball.
As an aside, the sensitivity setting doesn't do what you might think. All it does is change the power output of the LEDs in the sensor bar so that the remote can detect the sensor bar from farther away. It doesn't change how sensitive the remote is to hand movements. (The sensor bar doesn't actually sense anything; it just emits infrared that the remote can detect.)
far away from the good old days of the SNES when there where a ton of original and good games created.
Sorry to burst your bubble, but there is almost no chance of that happening again in your lifetime. When the SNES came out, video gaming was in its infancy. Basically everything was new. Now that we're a few decades into it, most games are seen as rip-offs or sequels because so much has already been done.
The other factor is that because of the technology involved, it's much more expensive to create a blockbuster game. In the Atari days, one guy could write a game in less than a month. What does it take now? Months of pre-production and design, followed by a couple years of building; teams of code artists and graphical artists and audio artists; millions of dollars spent in marketing. So the game makers play it safe and make stuff similar to what sold well in the past.
The next jump probably won't happen again until it's as easy to make a decent game as it is to write a decent novel: the work of a handful of dedicated people over the course of a few months. Maybe when we hit that point, we'll have as much variety in games as we do in literature.
Slashdot Mirror
Your other replier is wrong. There is another golf game, Super Swing Golf. I've read differing opinions on it, but haven't played it. It is, however, even more cutesy than Wii Sports golf.
They jacked the price up completely for their own benefit... but with no real reason!
I guess you must be very young, and have never taken an economics course. Although I'm sure some, or even most, of the people at Nintendo actually like making games, their purpose as a company is to make money. They aren't doing it just to make you happy. The reason, that you seem to think is missing, is to make money.
But like every company, they're going in for the whole "We'll charge more because we can. what's to stop us? people will still pay it."
This is how supply and demand works. The Wii is not necessary for survival. Therefore, if "people will still pay", those people must think the price is justified. Why should Nintendo lower the price if people will pay a higher one? They aren't running a gaming charity. They want to make money. And, as you said, people will still pay, because they think the price is worth it. Nintendo makes money, people still get their consoles. It's a win-win.
I've been using PowerShell for a couple months, and it's definitely better than cmd.exe. However, it's really built more like an interactive scripting environment, with shell features left as an afterthought.
Only the most basic redirection is implemented. Basically you can use "> file", "2> file", and "2>&1". That's it. You can't create arbitrary fd's and dup them. It's like they didn't realize that the '1' representing stdout and '2' representing stderr actually mean something more general. Oh, and no input redirection. Trying to do:
somecommand < file
gives you this error:
The redirection operator '<' is not supported yet.
At line:1 char:14
+ somecommand < <<<< test.txt
Although you can technically use "2> file" to redirect errors, it's actually a big pain. Say your program outputs to stderr for various warnings, and you want to capture those. Well because everything is an object, each error line is converted to an ErrorRecord object, which is then serialized. Unfortunately, the serialization of an ErrorRecord includes a bunch of other clutter. Here's an example of one error line:
> perl -e 'warn qq[Something bad happened!\n]' 2> out.err
> cat out.err
perl.exe : Something bad happened!
At line:1 char:5
+ perl <<<< -e 'warn qq[Something bad happened!\n]' 2> out.err
Three lines for every error, with a bunch of clutter to make it hard to read. In order to get succinct log files, I had to write my own ErrorRecord converter to get back to the one line I want.
Command argument parsing is broken. The parser will split arguments that look like "-x12.34". So if you try to pass a switch with a floating point number as part of it, the program actually receives two separate arguments: "-x12" and ".34". You have to quote the entire thing to get it passed as one argument.
One major annoyance with cmd.exe that has not been completely fixed is the quoting inconsistencies. Nested quotes don't seem to work right. In most shells, single quotes prevent any interpretation of the string, which is mostly true in PowerShell. So when writing a quick Perl one-liner, I use single quotes to make sure any Perl variables aren't interpreted by the shell.
perl -e '$k = "hello"; print $k'
That seems to work, and prints 'hello'. However, try adding a newline:
perl -e '$k = "hello\n"; print $k'
Now Perl gives me a syntax error regarding the backslash, which leads me to believe the shell is interpreting the string before handing it to Perl. In this case, I can work around it because Perl has its own quoting operators:
perl -e '$k = qq[hello\n]; print $k'
But how would you pass a string like this to some other program where you needed the quotes? I couldn't figure it out.
As a scripting environment, it's pretty nice. And like I said, it is better than cmd.exe. However, basic shell functionality is semi-broken in many ways, because of the focus on Being Innovative With Everything As An Object.
PS. Don't forget that the escape character is ` (backquote), and not \ (backslash) like in every other shell/language.
Try this simple procedure.
1. See the "20 Best..." or "15 Worst..." headline.
2. Immediately skip to the next article.
3. Profit!!
This got modded insightful?
Here's some insight for you: if the sound-generating toys annoy you so much, don't buy them. I doubt your two year old is buying his own toys. Get him some good old wood blocks or giant-sized legos. Not only will you get some quiet, it'll help him develop imagination instead of attention deficit disorder.
Okay sure, but what about the other point?
Suppose I run davidwristhegreatest.com.
First of all, who is going to visit "David Wrist He Greatest.com"? It's gibberish!
That's a few thousand people a year. Pretty soon that adds up to real money.
Second, how much do ad-views pay? One or two cents? Four people per day for a year would only be $14.60. Not sure that's a huge incentive.
But mostly it's the first issue. David Wrist He Greatest?? wtf?!
-you know who
McGrew??
Now if only I could figure out how to make vim map CAPS LOCK to CONTROL when it starts up, I'd have it made...
Better to just turn caps lock into control all the time, since caps lock is useless.
Here's a page giving directions: http://www.manicai.net/comp/swap-caps-ctrl.html
Or on Windows, search for the program KeyTweak.
You don't need a Dvorak keyboard. Most operating systems (including Windows and Linux) let you switch the key layout in software. Sure, the keys are labeled wrong at that point, but how often do you look at your fingers while typing?
The Vim thing isn't bad. Just remap some of the keys and it's fine. Although cut/copy/paste in most apps does get more annoying.
The biggest reason I've heard for switching is not quickness. It's finger-health. Since the keys are laid out with a regard for typing English, it's much easier on your fingers. Many words can be typed without leaving the home row.
-- Satisfied Dvorak user for 2+ years
Plenty of people are willing to take your money to support Debian for you, if that's what you want.
Your sig:
BSD code is free code to be used in software.
GPL code is code to be used in free software.
Although it makes the structure nice, using "free code" for the BSD case muddles the meaning. It would be more accurate to say:
BSD code is code to be freely used in software.
GPL code is code to be used in free software.
No, bogosort.
Well, thanks for trying. I guess you don't care about getting your point across, in which case there's no point in continuing this subthread.
Please point them out. Everything that I see being measured in that picture is perpendicular to the "camera" (it isn't actually a photo).
You've got to be perpendicular to the target square when you take the picture. How are you gonna do that with a tossed frisbee?
In Linux, you *have* to have a Start menu (or some analog).
I don't have one. I have a couple shortcut icons for commonly used programs and that's it. Uncommonly used programs are started from a command line widget next to my clock.
Linux advocates love to deride OS X...
Yet constantly, the Linux crowd comes up with nonsensical things...
This type of comment is worthless. The "Linux crowd" is not the Borg. It's made up of people with different tastes and interests. Some of them don't like aspects of OS X, and some of them do. It's not a contradiction.
Why don't you just use your pager and drag the small picture of the app to another desktop? Doesn't everyone using virtual desktops use a graphical pager?
The whole cube thing seems whizz-bang, but not particularly productive.
How about not compile? If equality isn't defined, the compiler shouldn't accept it.
What force could possibly be more dangerous
The Force. Specifically, the Dark Side.
I'll keep an eye out for the GCN games.
Pikmin 1 for less than $10: clicky
And no, I'm not the seller. I just think it's weird how many people have not heard of half.com (now run by ebay, as you can see from the link).
I haven't played either of them yet, but Excite Truck and Super Monkey Ball both use the controller tilt, as opposed to just detecting a random motion. In Excite Truck, you use the remote like a steering wheel to steer the truck, and tilting it forward or backward while in the air changes the tilt of the truck, which affects your landing. In Super Monkey Ball, the tilt of the remote changes the tilt of the floor to move your ball.
As an aside, the sensitivity setting doesn't do what you might think. All it does is change the power output of the LEDs in the sensor bar so that the remote can detect the sensor bar from farther away. It doesn't change how sensitive the remote is to hand movements. (The sensor bar doesn't actually sense anything; it just emits infrared that the remote can detect.)
far away from the good old days of the SNES when there where a ton of original and good games created.
Sorry to burst your bubble, but there is almost no chance of that happening again in your lifetime. When the SNES came out, video gaming was in its infancy. Basically everything was new. Now that we're a few decades into it, most games are seen as rip-offs or sequels because so much has already been done.
The other factor is that because of the technology involved, it's much more expensive to create a blockbuster game. In the Atari days, one guy could write a game in less than a month. What does it take now? Months of pre-production and design, followed by a couple years of building; teams of code artists and graphical artists and audio artists; millions of dollars spent in marketing. So the game makers play it safe and make stuff similar to what sold well in the past.
The next jump probably won't happen again until it's as easy to make a decent game as it is to write a decent novel: the work of a handful of dedicated people over the course of a few months. Maybe when we hit that point, we'll have as much variety in games as we do in literature.
Although it may not relate to your quote, you may be interested to know that wherefore means why .