The difference is the power of the console. Now you can get Wii-like games that actually look good. And the extra power allows a potentially much better interpretation of the inputs. That said though Sony isn't necessarily the best provider of tools and the hardware may or may not be on par. If the price of the PS3 can potentially go down and reach the level of "affordability" of the Wii, and developpers get enough support from Sony to use the interface efficiently this can be a kick ass combo.
...and everything looks better in black and white
on
Kodak Kills Kodachrome
·
· Score: 1
Easy?? You obviously don't write games for a living:-) There's nothing stopping anyone from downloading a patch on some pirate site that simply allows the gameplay to run connectionless. If you want to make it hard, content needs to be on the server end. Think MMO for single player. Now I'm not saying it's not feasible but it's FAR from easy and very very FAR from costless!
And you think no one thought about it??:-)
That's true until you come up at the end of the project and find out that the bulk of the process usage comes from the 90% of "coded un-optimized" portions that people felt free to overlook during the process.
If you write for any fixed hardware like a game console then the "add hardware" argument totally kills you. With that kind of problem you're pretty much screwed as you can't spend enough time going through every darn for loop in the project to optimize them so you ship with less framerate.
The point about this is that knowing your algorithms or how memory works in the background will have you avoid this problem. It won't slow down development at all but will make sure you don't end-up with a resource hog. I'm not saying to optimize to death, but rather that you should strive to write optimized if you can and it's not detrimental to the readability.
For instance, why use an algorithm that allocates objects dynamically when you can get away with a stack based one? Knowing this in advance will save your ass later.
It's a book by Charles Petzold that explains very well how computers work:
http://www.charlespetzold.com/code/
The rest depends on how apt your grandma is at grasping concepts.
Yeah the only reason I say it's easier as a kid is because that's the time of learning when anything you learn sinks in very deeply. Also times are relative, a session that looks looooooooong and booooring at 7yo will seem like a breeze at 30. I remember having to spends hours and hours of labor around the famility table during the holidays which really now are enjoyable. But I look at my nephews and they can't stand it!!;-) (mom! let's go! I want to leave!). Its just to illustrate the point that daunting tasks seem bigger as a kid then as an adult. Also you note that you did have to "switch" and the switch is what cost you, what if the kid's computers had already been qwerty or dvorak?
Anyway, we agree on most points;-) Have a happy holiday!
Someone calls a 53-key ABCD keyboard a "new standard keyboard" and suddenly people start to think that it will replace keyboards? ABCD keyboards have been around for a while and aren't any good for typing. As far as layout goes ABCD is as bad as QWERTY in terms of random placement of the keys.
The theory that it will "help kids learns" is bull. It might help grandma learn, but a normal kid will pickup any keyboard layout. This might as well be the DVORAK layout then, it's truly much better in terms of key placement.
Damn! But wait, why do I get ads with pay cable TV?
Learn DVORAK
on
Blank Keyboard
·
· Score: 2, Interesting
Learn DVORAK and keep your current keyboard. You'll never want to look at the keys anymore because they will confuse you. Result? You'll be typing without looking which is, according to the article, going to give you 100% faster typing (...) AND you'll be less prone to typing injuries AND it will cost you a whopping 0$!
What a bundle!
(just let the new layout sink-in for a few months)
Why would I be shelling out thousands of dollars on a wife when in millions of years women haven't changed that much?
I complain to my kids about this, and they insist that things have changed markedly. They show me examples, and all I see are breasts, butts and mostly stupid people.
The problem is that software makers tend not to care too much about security problems if it doesn't affect their sales. When a security concern gets published the fix priority jumps and get very important because the clients now have the choice of choosing a better product.
With this kind of judgment the security holes will become a guarded secrets amongst hackers and they will probably live a better life. Granted the hole will also less hackers but then again the ones that are actually capabable of exploiting the holes probably knew about the hole anyway.
Slashdot Mirror
The difference is the power of the console. Now you can get Wii-like games that actually look good. And the extra power allows a potentially much better interpretation of the inputs. That said though Sony isn't necessarily the best provider of tools and the hardware may or may not be on par. If the price of the PS3 can potentially go down and reach the level of "affordability" of the Wii, and developpers get enough support from Sony to use the interface efficiently this can be a kick ass combo.
Well apparently Paul Simon think it's better in black in white ;-)
http://www.youtube.com/watch?v=UcR_LvorN_0&feature=related
(2:02 mark)
http://en.wikipedia.org/wiki/Kodachrome_(song) ...
But still, Kodachrome gives us those nice bright colors
It gives us the green of summers
Make you think all the world's a sunny, oh yeah!
Easy?? You obviously don't write games for a living :-) There's nothing stopping anyone from downloading a patch on some pirate site that simply allows the gameplay to run connectionless. If you want to make it hard, content needs to be on the server end. Think MMO for single player. Now I'm not saying it's not feasible but it's FAR from easy and very very FAR from costless!
And you think no one thought about it?? :-)
That's true until you come up at the end of the project and find out that the bulk of the process usage comes from the 90% of "coded un-optimized" portions that people felt free to overlook during the process. If you write for any fixed hardware like a game console then the "add hardware" argument totally kills you. With that kind of problem you're pretty much screwed as you can't spend enough time going through every darn for loop in the project to optimize them so you ship with less framerate. The point about this is that knowing your algorithms or how memory works in the background will have you avoid this problem. It won't slow down development at all but will make sure you don't end-up with a resource hog. I'm not saying to optimize to death, but rather that you should strive to write optimized if you can and it's not detrimental to the readability. For instance, why use an algorithm that allocates objects dynamically when you can get away with a stack based one? Knowing this in advance will save your ass later.
It's a book by Charles Petzold that explains very well how computers work: http://www.charlespetzold.com/code/ The rest depends on how apt your grandma is at grasping concepts.
Yeah the only reason I say it's easier as a kid is because that's the time of learning when anything you learn sinks in very deeply. Also times are relative, a session that looks looooooooong and booooring at 7yo will seem like a breeze at 30. I remember having to spends hours and hours of labor around the famility table during the holidays which really now are enjoyable. But I look at my nephews and they can't stand it!! ;-) (mom! let's go! I want to leave!). Its just to illustrate the point that daunting tasks seem bigger as a kid then as an adult. Also you note that you did have to "switch" and the switch is what cost you, what if the kid's computers had already been qwerty or dvorak?
Anyway, we agree on most points ;-) Have a happy holiday!
Someone calls a 53-key ABCD keyboard a "new standard keyboard" and suddenly people start to think that it will replace keyboards? ABCD keyboards have been around for a while and aren't any good for typing. As far as layout goes ABCD is as bad as QWERTY in terms of random placement of the keys. The theory that it will "help kids learns" is bull. It might help grandma learn, but a normal kid will pickup any keyboard layout. This might as well be the DVORAK layout then, it's truly much better in terms of key placement.
Damn! But wait, why do I get ads with pay cable TV?
Learn DVORAK and keep your current keyboard. You'll never want to look at the keys anymore because they will confuse you. Result? You'll be typing without looking which is, according to the article, going to give you 100% faster typing (...) AND you'll be less prone to typing injuries AND it will cost you a whopping 0$! What a bundle! (just let the new layout sink-in for a few months)
Why would I be shelling out thousands of dollars on a wife when in millions of years women haven't changed that much? I complain to my kids about this, and they insist that things have changed markedly. They show me examples, and all I see are breasts, butts and mostly stupid people.
The problem is that software makers tend not to care too much about security problems if it doesn't affect their sales. When a security concern gets published the fix priority jumps and get very important because the clients now have the choice of choosing a better product. With this kind of judgment the security holes will become a guarded secrets amongst hackers and they will probably live a better life. Granted the hole will also less hackers but then again the ones that are actually capabable of exploiting the holes probably knew about the hole anyway.