I purchased this game along with my Wii. Having played most of the previous Zelda games (NESx2, Link to the Past, Link's Awakening, OoT, Seasons, Ages, Minish Cap, Wind Waker), I have a certain idea of what I expect in a Zelda game versus say Final Fantasy games. I am currently 9 hours in to Z:TP and have been sorely disappointed. Never before has Zelda included required+very difficult mini-games (sumo training, jousting, sumo match, etc). While I enjoy the main game, and the control scheme is pretty intuitive, these mini-games make me feel like I'm playing something other than Zelda.
The Zelda scheme has always been get item, use new item to beat dungeon, use new item to get to next dungeon, repeat. All sidequests/mini-games have been optional. That's what puts all the past Zelda's in the 'epic adventure' category of games. Z:TP falls in to the classic RPG category. While both are enjoyable, they should not be confused and Nintendo should not have moved Z:TP from epic adventure to RPG.
Excellent idea. In fact, I work at the law school's helpdesk attached to my university. Law students are required to have a laptop with certain minimum requirements. We've partnered will Dell to offer a purchase program where students get a large discount on the hardware and are required to purchase a 3-year "everything is covered, no questions" warranty (law school lasts 3 years). If a school requires students to have laptops, they also should have a certified helpdesk to repair said machines, and students should be strongly encouraged (read: required) to get a full-coverage warranty. The students will beat up the machines, and will not be happy if they have to pay $300-$400 for a replacement part a year after buying it.
A web farm made from wristwatches might not be useful on your enterprise network, but NetBSD can make old machines usable again. I recently bought a few SGI workstations (Indigo2's) from Boeing that were being surplused. Think I'm going to buy a $600 IRIX license (for each of 3 machines) for a computer that cost me $75? No. But I can download NetBSD and make the machines still useful. NetBSD running on an Indigo2 makes a fine small web or mail server. The parent said NetBSD rocks your bones. Bones... as in old computers (I'm just guessing)... Just because you don't give a shit doesn't mean the rest of us don't still see something as a useful product.
While I haven't read the above-mentioned book, "Effective C++", I have been forced to make the transition from C to C++ (at my University). Having a C background makes me see macros as one obvious solution to a problem, while they don't even teach macros in my C++ programming classes. Even talking to friends that program in C++ w/o starting out in C, it seems like C++ programmers are afraid of the preprocessor. Why is this? I'm not trying to be critical, I am genuinely curious as to why C++ programmers avoid macros and other preprocessor directives at all costs. Anyone have an explanation?
oh great... and I just got the original release of TTT from BitTorrent burned onto CD's. Now your telling me I have to go and redownload the whole thing? Thanks alot...:)
TinyOS sounds like a neat project, but I'll be more impressed when it gets ported to x86. I mean, even if the scheduler ballooned up to 500 bytes, the whole system would still be really small. Sorta like QNX.
That's right. Either fix the problems, contribute the new features or quit your bitching. That's the whole point of open source. You wanna "interject your opinion about the operating system you use on your computer" without being able to fix the problems, go run Windows.
I purchased this game along with my Wii. Having played most of the previous Zelda games (NESx2, Link to the Past, Link's Awakening, OoT, Seasons, Ages, Minish Cap, Wind Waker), I have a certain idea of what I expect in a Zelda game versus say Final Fantasy games. I am currently 9 hours in to Z:TP and have been sorely disappointed. Never before has Zelda included required+very difficult mini-games (sumo training, jousting, sumo match, etc). While I enjoy the main game, and the control scheme is pretty intuitive, these mini-games make me feel like I'm playing something other than Zelda.
The Zelda scheme has always been get item, use new item to beat dungeon, use new item to get to next dungeon, repeat. All sidequests/mini-games have been optional. That's what puts all the past Zelda's in the 'epic adventure' category of games. Z:TP falls in to the classic RPG category. While both are enjoyable, they should not be confused and Nintendo should not have moved Z:TP from epic adventure to RPG.
Excellent idea. In fact, I work at the law school's helpdesk attached to my university. Law students are required to have a laptop with certain minimum requirements. We've partnered will Dell to offer a purchase program where students get a large discount on the hardware and are required to purchase a 3-year "everything is covered, no questions" warranty (law school lasts 3 years). If a school requires students to have laptops, they also should have a certified helpdesk to repair said machines, and students should be strongly encouraged (read: required) to get a full-coverage warranty. The students will beat up the machines, and will not be happy if they have to pay $300-$400 for a replacement part a year after buying it.
A web farm made from wristwatches might not be useful on your enterprise network, but NetBSD can make old machines usable again. I recently bought a few SGI workstations (Indigo2's) from Boeing that were being surplused. Think I'm going to buy a $600 IRIX license (for each of 3 machines) for a computer that cost me $75? No. But I can download NetBSD and make the machines still useful. NetBSD running on an Indigo2 makes a fine small web or mail server. The parent said NetBSD rocks your bones. Bones... as in old computers (I'm just guessing)... Just because you don't give a shit doesn't mean the rest of us don't still see something as a useful product.
While I haven't read the above-mentioned book, "Effective C++", I have been forced to make
the transition from C to C++ (at my University).
Having a C background makes me see macros as one
obvious solution to a problem, while they don't
even teach macros in my C++ programming classes.
Even talking to friends that program in C++ w/o
starting out in C, it seems like C++ programmers
are afraid of the preprocessor. Why is this?
I'm not trying to be critical, I am genuinely curious as to why C++ programmers avoid macros and other preprocessor directives at all costs. Anyone have an explanation?
oh great... and I just got the original release of TTT from BitTorrent burned onto CD's. Now your telling me I have to go and redownload the whole thing? Thanks alot... :)
TinyOS sounds like a neat project, but I'll be
more impressed when it gets ported to x86. I mean, even if the scheduler ballooned up to 500 bytes, the whole system would still be really small. Sorta like QNX.
(It is a joke... laugh)
That's right. Either fix the problems, contribute the new features or quit your bitching. That's the whole point of open source. You wanna "interject your opinion about the operating system you use on your computer" without being able to fix the problems, go run Windows.
It could be an issue of proper drivers. If ya head
to Accel-X and
get a commercial-quality Linux X Server you might
get better performance.
So the specs are out... where can I download the
emulator, and is the NetBSD port done yet?