With the phone.com server and microbrowser you can send net alerts -- basically a link to a WML page which the phone immediately displays. This is an improvement over text only, one way SMS.
Yep, books are free. Newspapers are free. Radios and televisions and computers are free. Oh, hang on a minute...
What an incredibly erroneous comment.
Newspapers, TV shows, Radio stations make their money primarily off advertising. Would you like to have advertising in your software?
Software development is not journalism. You can pen an article in one night. To develop well, designed, feature rich software takes months (especially consumer targeted software).
Nothing prevents the Java 2D vendor's implementation from using hardware acceleration, and in fact it should indirectly do so already. For example, if the implementation makes calls to DirectDraw, than it should end up using acceleration. Ditto with Quicktime/QuickDraw.
I am so sick of people who mindlessly bleat that Java is slow. These people invariably have no idea what they're talking about. I have worked extensively with Swing, Java 2D, Enterprise Java Beans, Servlets, JSP, and more. I have also programmed in C and C++. I also like C and C++ but Java has an awful lot to offer (easy distributed apps with RMI, transaction support with EJB, elegant UI's with Swing, platform independence, a clean language... the list goes on).
Please go and download the Java 2D demo and watch real time anti-aliasing, alpha compositing, and bezier curve animations.
Please tell me why so many financial and ecommerce companies are building their services on EJB's, when Java is "plainly too slow".
There are projects where Java would be less or not appropriate -- device drivers, kernels, daemons.... For the rest, performance is perfectly acceptable, in my extensive experience.
The "too slow" argument can be further destroyed by pointing out that you can link and call native code from java, using JNI. So if you have a performance bottleneck -- such as a time-intensive algorithm -- you can write that algorithm natively and call it from java. It is rule of thumb that 90% of a program's execution time takes place in 10% of the code. If absolutely necessary (and normally it isn't), code that 10% natively and let the rest of your application take advantage of Java.
On the server side, most of the performance criticism is moot because scalability can be achieved through server clustering. Boxes can be added relatively inexpensively and easily as load increases.
Nobody can stop an idiot from writing a slow program in any language. If you know what you're doing, you can write an acceptably fast application in Java.
Slashdot Mirror
With the phone.com server and microbrowser you can send net alerts -- basically a link to a WML page which the phone immediately displays. This is an improvement over text only, one way SMS.
What an incredibly erroneous comment.
Newspapers, TV shows, Radio stations make their money primarily off advertising. Would you like to have advertising in your software?
Software development is not journalism. You can pen an article in one night. To develop well, designed, feature rich software takes months (especially consumer targeted software).
Software development is not content development.
If they resort to analog, music will either:
a). not be able to be played on a computer (e.g., in you're cd rom drive). Consumers will not stand for this.
b) will have to be converted to a digital signal, which can then be written to memory.
Sorry, even going to analog won't work.
Nothing prevents the Java 2D vendor's implementation from using hardware acceleration, and in fact it should indirectly do so already. For example, if the implementation makes calls to DirectDraw, than it should end up using acceleration. Ditto with Quicktime/QuickDraw.
Also, I disagree that the performance sucks.
I am so sick of people who mindlessly bleat that Java is slow. These people invariably have no idea what they're talking about. I have worked extensively with Swing, Java 2D, Enterprise Java Beans, Servlets, JSP, and more. I have also programmed in C and C++. I also like C and C++ but Java has an awful lot to offer (easy distributed apps with RMI, transaction support with EJB, elegant UI's with Swing, platform independence, a clean language... the list goes on). Please go and download the Java 2D demo and watch real time anti-aliasing, alpha compositing, and bezier curve animations. Please tell me why so many financial and ecommerce companies are building their services on EJB's, when Java is "plainly too slow". There are projects where Java would be less or not appropriate -- device drivers, kernels, daemons.... For the rest, performance is perfectly acceptable, in my extensive experience. The "too slow" argument can be further destroyed by pointing out that you can link and call native code from java, using JNI. So if you have a performance bottleneck -- such as a time-intensive algorithm -- you can write that algorithm natively and call it from java. It is rule of thumb that 90% of a program's execution time takes place in 10% of the code. If absolutely necessary (and normally it isn't), code that 10% natively and let the rest of your application take advantage of Java. On the server side, most of the performance criticism is moot because scalability can be achieved through server clustering. Boxes can be added relatively inexpensively and easily as load increases. Nobody can stop an idiot from writing a slow program in any language. If you know what you're doing, you can write an acceptably fast application in Java.