Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Siebel Systems (SEBL) - strong buy? -- Ignore unavailable to you. Want to Upgrade?

To: ahhaha who wrote (6507)	10/24/2002 2:15:40 PM
From: Hardly B. Solipsist	Read Replies (1) \| Respond to of 6974

My point wasn't .net vs J2EE, just the risks of getting involved with MSFT. The closer you get, the more likely they are to kill you. I would expect that .net is easier to use for the initial implementation, but MSFT products have a history of not scaling well and of having serious security problems, and I would be stunned if .net is any exception to this (after all, it runs on the same lousy MSFT operating systems). MSFT has spent a lot of energy on making easy things easy, but they frequently manage to make the hard stuff impossible in the course of that. My brother, who writes these kinds of applications for a living (I'm a systems programmer, so I know little about this high-level stuff) is much less impressed with the usefulness of .net than the person that wrote the message you quoted, but he is quite impressed with how slick it is. (But MSFT keeps trying, and they have an amazingly talented group of engineers, so maybe this time they'll get it right...)