Moving back to .NET

[Chris via Digitalmars-d]

On Friday, 25 September 2015 at 21:03:12 UTC, Laeeth Isharc wrote:

> And sensible mercantile consideration of what might go wrong 
> and what you are going to do if that happens - that's a very 
> different thing from what Chris was speaking about.  Because in 
> enterprises it's often the case that social and group emotional 
> factors are more influential day to day than rational 
> calculation.  (There is an extensive literature on this).  Of 
> course, everyone gives reasons for things - it's just that if 
> you observe closely those aren't the real reasons (and the 
> people themselves may be unaware of this).

Yep. What I was talking about was not the fear of a commercial 
failure because of having picked the wrong tool (management). I 
was talking about my impression that D might intimidate 
programmers/coders. One has to dedicate time to new (or at least 
different) concepts like ranges and templates, old "comfortable" 
concepts are questioned or no longer as relevant as people 
thought they were (e.g. OOP). On top of this, everything is still 
moving. And as if this wasn't enough to scare the sh*t out of 
people (tongue in cheek), the tools are so "basic" that your 
average Java/C# programmer who is used to the comfortable IDE 
world has to enter the dark realms of command line tools forged 
by Sauron.

Commercial risk is not that big a factor (Java was adopted by IBM 
very early), and there's always the option to interface to C, 
should D lack anything.

The only thing we can do is keep on keeping on (as Laeeth pointed 
out) and produce more and more quality stuff. Somebody has to do 
it. If we all had the same timid attitude towards adopting new 
technologies, D would no longer exist, nor would a whole bunch of 
other technologies.