SI
SI
discoversearch

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 (6506)10/24/2002 1:03:12 PM
From: ahhaha  Read Replies (1) | Respond to of 6974
 
Really? The below comments seem very pertinent about whether SEBL will benefit from their relation. Just what counts when trying to implement a CRM system?

June 18th, 2002 4:41 PM
A different view on the whole equation.

I run two developement teams, one Java team and one .NET team.

I find it interesting that most of the comments are from the Java comunity and specificaly about how bad Microsoft is. Are Java developers concerned that the only language they know now has some serious enterprise competition?

From my point of view, who cares. What concerns me and my client base is time to market, cost to implement and the cost to run and implement the project.

Having personaly been involved for the last 6 months in a huge .NET development project, and also for the last 12 months in a very large Java development project, both of which are for large global accounts, I can honestly say that the the following statements are true.

Time to market using .NET and the framework has been unbelievably fast (acomplished more in 6 months using .NET than we did in 12 months using Java and BEA)

Development team for the .NET development is a quarter the size of the Java team.

Cost to implement on MS is miniscule for a larger audience than it is using either BEA or WebSphere.


All our developers using Java have been developing core systems for over four years each, and other languages for longer, they know their stuff by now.

Our .NET development team consits of one senior developer 1 years experience in .NET the other developers had not been involved with .NET before the project and came from a VB / ASP development environment.

Most Java deployements we have run into trouble on the client side due to 'configuration issues' using BEA / WebSphere

Initial issues discovered during the deployement of .NET, all resolved within the first couple of weeks of the project, since then no deployement issues at all.

Cost to implement Java projects using Enterprise level application servers are simply unrealistic. JBoss can be used, and I am sure most developers would agree that it offers tons more functionality over commercialy available systems and is more stable and easily configurable, try telling a corporate account that they have no SLA's in place for their application server.

I personaly believe that the devide between the different languages and systems will at first evolve into a political decision within an organisation, and eventualy be decided on the three factors I mentioned above.

Lets be realistic, asking a prospecitve client, including internal departments to spend millions on licensing fees for application servers is a short term solution. Eventualy people wise up and the accountants find areas to cut back on.

I personaly am not a MS evangelist, I dont care either way, but I do try to be a realist for the sake of my clients and business I support.

Mike