Is this blogworthy ?;-)

Issue 1
Should we continue to write Stored Procedures or should we switch to Java?
Recently there has been quite a discussion and disagreement on this topic.
Should data management (or mismanagement ;-) ) must be as close to the data
Or
How much data processing should be done in the database and how much should be performed in the Java App logic code ?
Will you rely on a particular product or go the platform independence way of the world?
But what is your code need not be portable.
Doesn’t putting a lot of business logic into stored procedures break OO design?

Issue 2
Read clause 8 from the Microsoft Exchange Server doc

Copied here for convenience.

8. NOTE ON JAVA SUPPORT. THE SOFTWARE PRODUCT MAY CONTAIN SUPPORT FOR PROGRAMS WRITTEN IN JAVA. JAVA TECHNOLOGY IS NOT FAULT TOLERANT AND IS NOT DESIGNED, MANUFACTURED, OR INTENDED FOR USE OR RESALE AS ON-LINE CONTROL EQUIPMENT IN HAZARDOUS ENVIRONMENTS REQUIRING FAIL-SAFE PERFORMANCE, SUCH AS IN THE OPERATION OF NUCLEAR FACILITIES, AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL, DIRECT LIFE SUPPORT MACHINES, OR WEAPONS SYSTEMS, IN WHICH THE FAILURE OF JAVA TECHNOLOGY COULD LEAD DIRECTLY TO DEATH, PERSONAL INJURY, OR SEVERE PHYSICAL OR ENVIRONMENTAL DAMAGE.

Is that a marketing gimmick or does Microsoft mean that SUN killed a bit of Microsoft or are you going to stop using Java!?

Issue 3
With Sun and Google supporting each other on every front including Gosling talking about extending support for Ajax, will Yahoo and Microsoft join hands?

Issue 4
Are you impressed with a Geek trying to develop an Ajax framework using the concept of event queue, just to go gaga seeing separation of event handling from the actual page? Are you thinking he is a fool or are you considering the scalability, cost and efficiency of this queue pattern model?


Now why did I have to do this? Anyways, thanks to www.google.com
Disclaimer:
None of these opinions are my own!