On Nov 28, 2007 4:04 PM, Joel Reymont <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:<br>> I may be wrong here but the advantages of using Java over Erlang for<br>> the CIO lie not so much in the technical merits of Java as in the deep
<br>> pool of Java developers.<br><br>On Nov 28, 2007 4:11 PM, Sean Hinde <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:<br>> My experience has shown that if you want to persuade a CIO of this
<br>> mindset to use a new fancy programming language, then the choice of VM<br>> is a detail of miniscule importance.<br><br>> Arguments are much more about support, availability of programming<br>> resource (including option to outsource if the in house team proves
<br>> too troublesome or expensive) etc etc.<br><br>I was silently referring to outsourced or ready to buy solutions. Where CIO dream about: No in-house development but outsourcing and buying solutions. And technologies like SOA, etc. give you interoperability.
<br>I was approaching the topic rather from the external integrator's view - not from the internal perspective. And then the pool of developers, support, etc. is your problem regardless of your solution's programming language.
<br><br>Your customer's CIO wants a solution which works, is cheap, future proof, reliable and fits into the company's strategic and environment. Not necessarily in this order.<br>Under this scenario the least they want to do is to touch your solution's code. Which makes the underlying programming language not _that_ important. More important are of course your qualities as an integrator/solution provider (many different aspects) and: Does this solution fit into my environment? Is this VM really stable? Who is Ericsson? (SCNR) Can we trust the solution's stability given that not many other companies have any experince with it and my CIO magazine never mentioned a product based on the whole concept? Is it based on technologies we already use or do I have to send all our admins to courses? Etc, etc.
<br><br>If we can say, our solution is based on Erlang but it runs in your well known and proven Java environment, you can much easier give answers to their questions. BTW: this is also true if you see it from the internal viewpoint.