The only benefit is being able to aim the Wiimote to aim the bow etc, but that's actually a down side if you don't have a super-gigantic television. You're not allowed to use the Wiimote from close enough to make it easy.
That sucks. When I think back to the times of the old Donkey Kong arcade, Nintendo's start into the business, that's a huge step backwards. The feel of controlling Mario was unparalleled at that time. How little do they pay attention to the fun factor nowadays. Everytime a video game makes me angry, I wonder why I keep playing such things at all. The player should have fun playing, not gnash their teeth at having to play the same stupid scene for the umpteenth time, just because it is too hard for the casual player. (The scene in TP when you have to guard the wagon of the sick prince comes to mind; I completed it once only out of sheer luck after hundreds of failed attempts; to me, that's not the meaning of fun
In Okami they managed to foul up a wonderful game with a series of stupid minigames that have nothing to do with the game itself. But you cannot proceed if you don't complete these minigames. Regardless, I at least managed to complete Okami after 50+ hours of gaming. But the replay value is drastically reduced if you have to fear to play those minigames again...
lately I've had urges to go out and ride a bike (just got one for the first time in like a decade.)
Indeed, riding a bike can be lots of fun. I did that a lot when I was younger, and it added a lot to my life.
A couple of years ago, I broke a leg doing a harmless thing, because my lack of movement had eroded my leg muscles, and now I have sheet metal in my leg and can never ride a bike again, I cannot bend my leg as needed anymore!
More seriously, what games do you know of that don't piss on you?
I don't know
Okami was quite good in retrospect (except the minigames).
Halo I & II perhaps
Most recently I've been playing Grand Theft Auto: San Andreas over again, because I had to reformat my Xbox and forgot to back up my saves, and I have to say it's a pretty great game, it's very rarely cheap and rarely do they give you a mission that can't be improved by a little forethought.
Yeah, it's quite okay -- the only thing for me to complain about in that game is the lack of realism. Like when cops appear out of nowhere right behind you, or when pedestrians walk only the same road you are on, disappearing around the next block. Only some houses can be walked into
Halo and Halo 2 both lack subtitles. Some of us need to play with the volume off
That's a problem affecting most of the games. They're useless without sound. In Halo and other FPS, you need to hear the enemy approaching
What I want most at this point in my life is a game that's not horribly cheap, that's fun to play, that allows me to save any time (GTA fails on this count.)
Yeah, I want that too. And I'm also annoyed if I cannot save at arbitrary points. I'm a programmer, and once I had to tell an acquaintance who's game programmer how to save the level information. My goodness, is that so difficult? To save a couple of positions?
If game development nowadays wouldn't be so time consuming, I would make some really good ones!
BTW, one the best of the cheap game saving methods I found in Okami. It doesn't save the exact position of the wolf, but there are so-called "memory gates" which store your memory when you walk through. If you die, you're resurrected at these points. You can also save at every teleport mirror. Luckily, these are spread around at strategic places, so you never have to worry of replaying an entire level if you die. Also, the wolf has to eat to keep her stomach full, and she doesn't die when she still has life force in her. That's one of most elaborate "life" concepts in games I've seen.
the games I'm playing most now are Wii Sports and Wii Fit. In our household Wii both could stand to lose a few pounds. I think that's where the name of the console really game from
Yup, don't neglect your health, especially if you're overweight!
This avoids especially knee problems (which I know first hand!
If you force convergence towards a single set of APIs for everything, you destroy any usefulness that the study of computer science and its related fields can offer.
How so? The API (the interface) does not prescribe how its implemented. Implementation can always vary.
Furthermore, new APIs can be considered at any time. However, a standard interface never changes in a way that breaks compatibility.
Having said that, we already have a set of standard APIs for threading and most OS-level operations. It's called POSIX.
POSIX conformance is not just a matter of supporting a specific function, but also if the function behaves according to the standard. On GNU, Linux, et al., this is still being worked on.
Not so long ago, Linux provided a poor implementation of the POSIX standards (especially regarding threads, signals, and asynchronous I/O), and was far behind BSD, Solaris and AIX. Solaris too suffered from many problems. For some years, AIX was the only UNIX-like OS that I've seen that provided a reasonable implementation of these features. BSD also seemed pretty good when I used it for some years. Gladly for us developers, Linux has been catching up in the past years, however. Manual pages have been cleaned up to provide less misleading information also, a good development.
The POSIX subsystem of Windows is (like Windows) of poor quality, and is not fully installed by default. I still remember the times when fork() didn't work (don't know if they fixed it). Methinks, Microsoft should throw out their proprietary kernels and use a UNIX-like kernel (a BSD, Linux, or Mach kernel). The Windows program loader and task scheduler still have some serious defects (as of Windows Vista). Like, it's not possible to terminate a process cleanly from the outside (disrupts DLL reference counters, for instance), programs are loaded in whole (leading to catastrophic performance during startup), and the task scheduler often switches away from a process for a long time (often with 50 ms delay whereas on Linux it's below the 1 ms granularity level), which makes it difficult to write timing sensitive applications on Windows.
Finally, we've had a standard windowing system (and associated GUI toolkit) since late 1987. It's called X11. I don't understand why Apple and MSFT decided to reinvent the wheel.
Microsoft made some grave mistakes during the 80ies, which are still affecting us today. Like, a virtual machine (while slow at that time), could have provided 32-bit environments already on 16-bit CPUs (a lesson learnt decades ago, in the 60ies, from the computers that existed back then: in a resource-constrained environment, provide a virtual environment circumventing the constraints). At least a 32-bit DOS could have been developed (Microsoft made an alliance with IBM on OS/2 but neglected its DOS). Thus, a number of incompatible DOS-extenders emerged, providing at least 32-bit addressing on 32-bit CPUs. Thus, Windows 1.x-3.x had to support 16-bit, and thus were written mostly with 16-bit environments in mind. There existed a 32-bit extension, called Win32s, but it was hardly used, for, at the time, 32-bit OSes had already been available from Microsoft. The idiocy goes on and on
A UNIX-like Windows could have saved the industry trillions of dollars, and hundreds of thousands of businesses would not have gone bankrupt due to costs related to Windows problems.
What API are you talking about? (...) are you talking about the numerous sanity and feature-presence checks that cmake and autotools much do due to differing APIs and software loads between various platforms and sites?
Exactly that. Hundreds of thousands up to millions of different API functions exported by ten thousands of libraries in their many (often incompatible) versions. There must be a consolidation of some sort someday, a convergence towards a predictable set of APIs. This is already happening, but at the current pace it will take years or decades to complete.
There's an easy way to deal with that... target a single platform and software load.
That's not an option if a program must be portable.
I haven't seen this. The apps on my system are written in one of: C, Python, Perl, C++, Ruby, Java. (I have exactly one Java application on my systems: Azureus (nee Vuze).)
Then you've missed out on the recent software industry trend towards C# even on Unix platforms (through Mono, a
Regardless, how does moving away from C/C++ to Java resolve this "standard API" issue that you're talking about? Perhaps a more specific definition of "standard API" would be helpful.
API = application programming interface
Standard API = standard application programming interface
The C and C++ have been standardized too late a point in time, and the shock waves are still perceivable. Only in the past few years, compilers like GCC reached halfways compliance with C and C++ standards. Especially on UNIX-like systems, adoption of standards has been slow. Add to that the ineptitude of the standards comittees to provide standard libraries for vital aspects of real-world programming like multithreading and graphical user interfaces. Merely C/C++ bindings to existing standards in these parts would have been sufficient, perhaps with a reference implementation.
I've been working with C since 1986 and with C++ since 1992, and I have seen plenty of changes. It is funny how slow things can evolve in this fast-paced industry.
"You'll pay to know what you really think." -- J.R. "Bob" Dobbs