I wonder if Jack Valenti is going to sue Al Qeda for inserting footage of terrorist training videos in the middle of holywood movies and distributing them around the world.
http://www.miami.com/mld/miamiherald/3898012.htm
MPAA -- Allies in the war against terrorism.
How would I go about replacing my regular land line with VOIP? Do I have to sign up with a VOIP phone service provider? I've looked at all of these pages, but none of them actually tell you how to use them.
I'm actually working on a book about BREW development and I disagree. BREW may fail, but not for these reasons.
J2ME works in the same way--only worse. You have to get your application certified by every single carrier you wish to carry it. Nevermind the fact that carrier relationships are increasingly harder to get these days.
With BREW, you just need to get True Brew Certrified by Qualcomm's hired testing lab, and that's it. You still need to get carrier relationships, but all BREW carriers adhere to the True Brew testing standards.
The biggest problem with BREW (aside from the lousy hardware) is the development tools. You have to pay for a $1500 compiler that should be free (why not use GCC for ARM?) and a $400 Verisign account for no apparent reason. I understand the need to digitally sign your applet for distribution, but you still need to generate certificates just to test it. The emulator is totally inaccurate, and there is no way to debug your code on hardware.
Unlike Java, BREW is a C/C++ API cross-compiled for the chipset. So you're likely to get crashes on the device that you don't get in the emulator. The problem is, there's no way to step through code on the device. You can't even so much as get a printf from the handset to the host PC. (J2ME does this at least! Some J2ME devices even have debug VMs that let you stetp through code on the device!)
The API is actually way better than J2ME for games. J2ME is still a zillion easier to get running on a real handset, and thus I'll have to give the nod to J2ME early on as a develoment environment.
But don't count BREW out.
After all, Verizon Wireless is the #1 carrier in America. And BREW is already #2 in Korea, which is the second largest mobile gaming market on the planet. And probably will be for quite some time.
Slashdot Mirror
I wonder if Jack Valenti is going to sue Al Qeda for inserting footage of terrorist training videos in the middle of holywood movies and distributing them around the world. http://www.miami.com/mld/miamiherald/3898012.htm MPAA -- Allies in the war against terrorism.
How would I go about replacing my regular land line with VOIP? Do I have to sign up with a VOIP phone service provider? I've looked at all of these pages, but none of them actually tell you how to use them.
As far as I know, it has been illegal to sell used CDs and video games in Japan for years. Welcome to your future.
I'm actually working on a book about BREW development and I disagree. BREW may fail, but not for these reasons. J2ME works in the same way--only worse. You have to get your application certified by every single carrier you wish to carry it. Nevermind the fact that carrier relationships are increasingly harder to get these days. With BREW, you just need to get True Brew Certrified by Qualcomm's hired testing lab, and that's it. You still need to get carrier relationships, but all BREW carriers adhere to the True Brew testing standards. The biggest problem with BREW (aside from the lousy hardware) is the development tools. You have to pay for a $1500 compiler that should be free (why not use GCC for ARM?) and a $400 Verisign account for no apparent reason. I understand the need to digitally sign your applet for distribution, but you still need to generate certificates just to test it. The emulator is totally inaccurate, and there is no way to debug your code on hardware. Unlike Java, BREW is a C/C++ API cross-compiled for the chipset. So you're likely to get crashes on the device that you don't get in the emulator. The problem is, there's no way to step through code on the device. You can't even so much as get a printf from the handset to the host PC. (J2ME does this at least! Some J2ME devices even have debug VMs that let you stetp through code on the device!) The API is actually way better than J2ME for games. J2ME is still a zillion easier to get running on a real handset, and thus I'll have to give the nod to J2ME early on as a develoment environment. But don't count BREW out. After all, Verizon Wireless is the #1 carrier in America. And BREW is already #2 in Korea, which is the second largest mobile gaming market on the planet. And probably will be for quite some time.