- Yahoo Daily News: Eat Curry and Be Happy
- Motley Fool: Applying Football Rules to Investing
- CNN: Senator Blue
Dot Net? or Dot Not?
I am meeting a Microsoft.NET Evangelist tomorrow. In preparation for the meeting, I have read up quite a bit on Dot Net stuff. I am looking for some specific answers, most importantly why I shouldn't abandon Microsoft completely and build Java apps instead.
If Dot-Net were to fly, much of my software will become obsolete. This is an issue that has occupied my mind for the last two years a lot, and I am eager to decide one way or the other...
My Requirements (really, our customers' requirements)
- Support for client heavy computing -- support for pictures, documents (rich-text), and printing
- Easy deployment -- I do not want to ship binary runtime with my app. This is my biggest problem with Java.
- Much of our software is rule-based. This means I want robust scripting. Compilation, Just-in-time compilation is all meaningless in my domain. I want to be able to specify code on the fly and execute it.
- My other requirements are same as that for other people - performance, cost, rapid development, durability of the platform, and reliability
