I'm not well versed in what the standish group has to say on a broad range of topics, but I know they gave a very fair review of Solaris vs. NT (link of main page). They basically concluded that Unix is still much better all around, confirming what many of us already know. I think in this case they simply have narrowed the focus.
This may be a consequence of many Linux users who are quick to claim that Linux can fulfill every desire and niche for medium to high end computing. There are a lot of arrogant claims, and someone like the Standish Group is bound to call the bluff.
This is still very good news, but the vendor is probably still paying Microsoft for an OEM copy of windows, which in turn is paid by the consumer. This is a good step in the battle, but the real win comes when Microsoft doesn't earn money from every computer sold, regardless of the operating system installed.
I too found his comments on Java, detailed in VNU.net to be off base. Call Java what you want, the fact is that it is very hot and a large part of the developer community is behind the momentum.
You can also use IBM's websphere, although I haven't heard much about it. You can run Sun's Java WebServer on Linux or other Java 1.1.6 enabled systems, but Sun will only Support it on Solaris or NT. My experience with JWS is that it is a little slower than Apache (I haven't pushed it really hard though) but it is easy to set up. A caveat - I've been administering Apache servers for over two years, so I'm speaking from experience, not bellyaching about anything.
The Java Web Server costs $300, and Apache is free. Consider the cost of JWS as a support cost in case you need it... which is rather cheap as support goes.
There is a short section about how to use Servlets with Java Beans, however since the Enterprise Java Beans API isn't officially released they don't have specific info on that. The introspection examples with Java Beans are pretty good.
No, the book doesn't provide much advice for setting up servlets, and they take the easy road out by doing development with Sun's Java Web Server. The book is geared toward the developer, but it doesn't help with building Jserv or any other engines.
From personal experience, I tried for a long time (about 3 weeks with many rebuilds) to set up the Apache Jserv on Solaris with Apache 1.3.4 and could never get it to work. I was able to get Apache and JRun (from www.livesoftware.com) to work, but some things were flaky with the class loader.
I'm not doing my testing with Sun's Web Server. Don't get me wrong, Apache rules. I would rather use Apache, but if you want to use Servlets with ease and get going without much headache, the Java Web Server is really quite good. It is a nice alternative if you can't get Jserv or JRun working right.
Just to echo the reviewer's thoughts... I just finished reading this book and I am *very* impressed. I don't plan on writing a cgi script again as long as I can use servlets. The book is probably the most thorough I've read about a specific Java topic.
For my web site development I plan to use PNG in the future, along with Java Servlets. Three main ideas bounce around in my head:
1. store all graphics as postscript and run a converter (via Servlets) which preprocesses the page and delivers a [.gif|.jpg] or.png based on browser support.
2. store graphics as.gif or.jpg and use the servlet to convert to convert to.png if the browser supports it.
3. store separate, but equivalent copies of image.gif and image.png and use a servlet to choose the right graphic based on browser support.
I like solution number 1 the best, and I'm anticipating using PNG in the future. I believe that maintaining copyright might be important sometime, and PNG makes that easier for the content deliverer.
That sort of application which resides on each users desktop and fills in the textual inforation is called a web browser.... it's already there!
no flame intent here, i understand what you mean about how an app could have more interesting content, but i think it is cool how i can access/. from anywhere with a browser. common denominator, but it is still very functional.
If you want to appeal to Solaris users who visit the site, you could make one of the optional sidebars listing news from Solaris Central (www.SolarisCentral.org).
I operate the site and would be glad to provide the text and links in a flat file if that would make things more convienent for you. mail me if you are interested.
That article was way too kind to divx. they neglect to mention the many reasons why informed customers hate divx. imagine trying to play your movie at a friend's house, only to find out that the movie you bought only works on your machine. what happens when you service a machine? If you like pan & scan and lower picture quality and to pay each time you view... go for divx. otherwise, dvd is the obvious choice.
I have a DVD player and personally choose not to purchase anything at circuit city because they endorse divx. Seriously, divx is evil stuff concocted by lawyers.
Slashdot Mirror
I'm not well versed in what the standish group has to say on a broad range of topics, but I know they gave a very fair review of Solaris vs. NT (link of main page). They basically concluded that Unix is still much better all around, confirming what many of us already know. I think in this case they simply have narrowed the focus.
This may be a consequence of many Linux users who are quick to claim that Linux can fulfill every desire and niche for medium to high end computing. There are a lot of arrogant claims, and someone like the Standish Group is bound to call the bluff.
This is still very good news, but the vendor is probably still paying Microsoft for an OEM copy of windows, which in turn is paid by the consumer. This is a good step in the battle, but the real win comes when Microsoft doesn't earn money from every computer sold, regardless of the operating system installed.
I too found his comments on Java, detailed in VNU.net to be off base. Call Java what you want, the fact is that it is very hot and a large part of the developer community is behind the momentum.
You can also use IBM's websphere, although I haven't heard much about it. You can run Sun's Java WebServer on Linux or other Java 1.1.6 enabled systems, but Sun will only Support it on Solaris or NT. My experience with JWS is that it is a little slower than Apache (I haven't pushed it really hard though) but it is easy to set up. A caveat - I've been administering Apache servers for over two years, so I'm speaking from experience, not bellyaching about anything.
The Java Web Server costs $300, and Apache is free. Consider the cost of JWS as a support cost in case you need it... which is rather cheap as support goes.
There is a short section about how to use Servlets with Java Beans, however since the Enterprise Java Beans API isn't officially released they don't have specific info on that. The introspection examples with Java Beans are pretty good.
No, the book doesn't provide much advice for setting up servlets, and they take the easy road out by doing development with Sun's Java Web Server. The book is geared toward the developer, but it doesn't help with building Jserv or any other engines.
From personal experience, I tried for a long time (about 3 weeks with many rebuilds) to set up the Apache Jserv on Solaris with Apache 1.3.4 and could never get it to work. I was able to get Apache and JRun (from www.livesoftware.com) to work, but some things were flaky with the class loader.
I'm not doing my testing with Sun's Web Server. Don't get me wrong, Apache rules. I would rather use Apache, but if you want to use Servlets with ease and get going without much headache, the Java Web Server is really quite good. It is a nice alternative if you can't get Jserv or JRun working right.
Just to echo the reviewer's thoughts... I just finished reading this book and I am *very* impressed. I don't plan on writing a cgi script again as long as I can use servlets. The book is probably the most thorough I've read about a specific Java topic.
For my web site development I plan to use PNG in the future, along with Java Servlets. Three main ideas bounce around in my head:
.png based on browser support.
.gif or .jpg and use the servlet to convert to convert to .png if the browser supports it.
1. store all graphics as postscript and run a converter (via Servlets) which preprocesses the page and delivers a [.gif|.jpg] or
2. store graphics as
3. store separate, but equivalent copies of image.gif and image.png and use a servlet to choose the right graphic based on browser support.
I like solution number 1 the best, and I'm anticipating using PNG in the future. I believe that maintaining copyright might be important sometime, and PNG makes that easier for the content deliverer.
That sort of application which resides on each users desktop and fills in the textual inforation is called a web browser.... it's already there!
/. from anywhere with a browser. common denominator, but it is still very functional.
no flame intent here, i understand what you mean about how an app could have more interesting content, but i think it is cool how i can access
If you want to appeal to Solaris users who visit the site, you could make one of the optional sidebars listing news from Solaris Central (www.SolarisCentral.org).
I operate the site and would be glad to provide the text and links in a flat file if that would make things more convienent for you. mail me if you are interested.
You might also want to check out a article in The Register about this. Keep an eye on Solaris Central for updated news on this issue.
That article was way too kind to divx. they neglect to mention the many reasons why informed customers hate divx. imagine trying to play your movie at a friend's house, only to find out that the movie you bought only works on your machine. what happens when you service a machine? If you like pan & scan and lower picture quality and to pay each time you view... go for divx. otherwise, dvd is the obvious choice.
I have a DVD player and personally choose not to purchase anything at circuit city because they endorse divx. Seriously, divx is evil stuff concocted by lawyers.