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: Hardly B. Solipsist who wrote (6508)	10/24/2002 2:34:06 PM
From: ahhaha	Read Replies (2) \| 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 don't know of any evidence for this. The government couldn't find any. If what you claim is true, SEBL is wise to get on MSFT's side because it reduces the possibility that MSFT will invest in a firm who uses dotNET to do CRM. 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). Yawn. I heard all that 7 years ago. XP is lousy? How far can you go with J2EE? It makes you think you can go far and then you run into all these problems near the end of your project. Development time then starts expanding as you feverishly look for an answer that will work. 90% of engineers are wasting time trying to put that last piece together. They're motivated by one thing: hatred of MSFT. They can't be objective. 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. You can do a lot with easy things, but you find you can't do much with harder things because it's too hard to get it to run right at the edge. Better to cobble together simple with the implied hit on performance in trade-off with uptime. 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. At the CRM level you need "slick" and you need "simple". The lack of these has been the cause of insurmountable problems for SEBL. dotNET makes these problems surmountable (But MSFT keeps trying, and they have an amazingly talented group of engineers, so maybe this time they'll get it right...) You should challenge my claim that dotNET is the prime lever for CRM.