What happens when it's time to start actually making money off the thing, and you have to hike the price back up to $400-500? If you're eating a couple hundred bucks loss per unit, you can't exactly make that up on volume.
That's what I mean. Why isn't it just getting that info from the OS? Is Java still actively supported on any operating systems that don't have some kind of time zone database? Sounds like not-invented-here syndrome to me.
I have a hard time believing that Java has no problem abstracting an operating system's graphics, sound, console I/O, network I/O, etc. into a portable API, but somehow can't manage the same for timezone info.
Yeah, but in the case of the NES, you can disable it by clipping a single chip pin on the board, and for the SNES, just Dremel off a little bit of plastic in the cartridge slot. And typically, these games would be timed to the video refresh rate, so switching between NTSC or PAL will usually cause the game to run at the wrong speed.
So what you're saying is that they should reduce marketing, spend more on training and staffing, and shrink the clientele, while at the same time lowering prices? Interesting strategy, but I don't think "reduce revenue and increase operational overhead" would have the desired result.