Where will D sit in the web service space?

[Paulo Pinto via Digitalmars-d]

On Monday, 13 July 2015 at 16:13:08 UTC, Dmitry Olshansky wrote:
> On 13-Jul-2015 18:55, Paulo Pinto wrote:
>> On Monday, 13 July 2015 at 15:10:08 UTC, Kagamin wrote:
>>> On Monday, 13 July 2015 at 07:32:57 UTC, Paulo  Pinto wrote:
>>>> Regarding D, there needs to be a story to be sold (e.g 
>>>> Docker, Rails,
>>>> next Firefox,iOS, Android, WP...) why the language matters.
>>>>
>>>> On my little world, customers choose programming languages 
>>>> because
>>>> they want to
>>>> use tool X, framework Y or target operating system Z.
>>>
>>> Doesn't that mean the language doesn't matter?
>>
>> I guess you didn't get my point.
>>
>> iOS app => Objective-C. Eventually Swift.
>
> Well, there is Xamarin C#. And any scripting langauge once you 
> fit a VM
>  in Objective-C (superset of plain C). LUA is quite popular.
>
>>
>> Windows desktop => Mostly C#. Some C++ and C++/CX.
>>
>> Hadoop => Java
>>
>> Android => Java
>>
>> JSF => Java
>>
>
> JVM more preciesly I think.
>
>> Sharepoint => C#
>>
>> ....
>>
>> That is how we get to choose languages. The elected one is a 
>> consequence
>> of the ecosystem being chosen, not the other way around.
>>
> That is a valid point to a certain degree.

I am speaking of my experience in the enterprise world and really 
meant the languages I have written, not your alternatives.

We seldom do greenfield projects.

We get to pick where the previous contractors left the project, 
as well as, the next ones get to pick where we left it.

So customers choose the ecosystems official languages to minimise 
attrition, and not what might work as well.