<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>Yet provided no proof that changing the word Telecom would improve adoption or that it hurts adoption.<br></div>
<div> </div>
<div>Additionally no proof that causing adoption based on some name changes and marketing are a good thing.<br></div>
<div> </div>
<div>There was a boon in Erlang usage some 5 years ago that left a sour taste in many peoples mouths because it was incorrectly used for problems that both fit the language and those that didn't.<br></div>
<div> </div>
<div>Time is better spent building systems and tools than naming or trying to ride a wave of 'reactive' or 'async' or whatever else is the fad at the time.<br></div>
<div> </div>
<div>Sun did a great job with pushing Java into realms it wasn't built for. I want increased adoption, but for the right reasons.<br></div>
<div> </div>
<div> </div>
<div>On Thu, Feb 13, 2014, at 10:22 AM, kraythe . wrote:<br></div>
<blockquote type="cite"><div dir="ltr">Ahh well. I have had my say and stated my opinions more than once. So I can leave it there. It is, however, definitely food for thought about the direction I wish to go with my project. Not so much the issue of OTP as a name but the general impression of "adoption? bah humbug ... if they don't like it they all suck and we don't care." Sounds like a disaster of a business decision to me. <div> </div>
<div>Im not so sure its going to be easy to staff or finance a project on a language that has 1) tools that need work, 2) a limited trained staff 3) a community that cares little about language adoption. It could be that Erlang becomes another Lisp for me. A language I think rocks but is entirely impractical in the business world. <br></div>
<div> </div>
</div>
<div><div> </div>
<div><div dir="ltr"><div style="font-family:arial;font-size:small"><b>Robert Simmons Jr. MSc. - Lead Java Architect @ EA</b><br></div>
<div style="font-family:arial;font-size:small">
<i>Author of: Hardcore Java (2003) and Maintainable Java (2012)</i><br></div>
<div><i style="font-family:arial;font-size:small">LinkedIn: </i><span style="font-family:arial" class="font"><i><a href="http://www.linkedin.com/pub/robert-simmons/40/852/a39" target="_blank">http://www.linkedin.com/pub/robert-simmons/40/852/a39</a></i></span><br></div>
</div>
</div>
<div> </div>
<div> </div>
<div><div>On Thu, Feb 13, 2014 at 12:16 PM, Miles Fidelman <span dir="ltr"><<a href="mailto:mfidelman@meetinghouse.net" target="_blank">mfidelman@meetinghouse.net</a>></span> wrote:<br></div>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><div>Miles Fidelman wrote:<br></div>
<div> </div>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
kraythe . wrote:<br></div>
<div> </div>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
I have told you my "green" impressions of OTP and you can dismiss them if it make you more comfortable but it wont change the fact that others will have those feelings and many will not get on the list and go further. They will simply move to Ruby, Scala, Node.js, Clojure, or something else. If our attitude is "I didn't want you in the community anyway!" then Erlang will be the next Smalltalk or Lisp. Of academic and little more than that in significance.<br></div>
<div> </div>
</blockquote><div> </div>
<div>
Bah, humbug. As long as there's a need for industrial strength massive concurrency, and no serious alternative, it doesn't really matter what it's called.<br></div>
<div> </div>
<div>
Anybody who tries to write a massively concurrent application in Ruby, Scala, Node.js, Cojure (or Java for that matter), gets what they deserve.<br></div>
<div> </div>
<div>
Just one man's opinion, of course.<br></div>
<div> </div>
<div> </div>
</blockquote><div> </div>
</div>
For that matter, what's with this trend toward renaming things - all it does is confuse people (think Accenture vs. Anderson Consulting).<div><div> </div>
<div> </div>
<div> </div>
<div>
-- <br></div>
<div>
In theory, there is no difference between theory and practice.<br></div>
<div>
In practice, there is. .... Yogi Berra<br></div>
<div> </div>
<div>
______________________________<u></u>_________________<br></div>
<div>
erlang-questions mailing list<br></div>
<div>
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br></div>
<div>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/<u></u>listinfo/erlang-questions</a>
<br></div>
</div>
</blockquote></div>
<div> </div>
</div>
<div><u>_______________________________________________</u><br></div>
<div>erlang-questions mailing list<br></div>
<div><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br></div>
<div><a href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a><br></div>
</blockquote><div id="sig19305637"><div class="signature">-- </div>
<div class="signature"> Tristan Sloughter</div>
<div class="signature"> tristan.sloughter@gmail.com</div>
<div class="signature"> </div>
</div>
</body>
</html>