Re: Collateral Damage

Michael Malter <[email protected]> Mon, 25 Apr 2022 17:44:56 +0200
Newsgroups gmane.comp.lang.erlang.general
Message-ID <CADE9FeH8ADSvmUJPrBNrHmYMv7zAhKP1S9BOmB3FzfBB=nACmw@mail.gmail.com>
--000000000000f7f2bb05dd7c75a5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Experience. Over the years I have developed a workflow around Erlang. So
yes, I am faster in Erlang. To be clear, thee main reasons are :
- the way my text editor is configured
- the testing philosophy in elixir (which I find horrible but maybe that's
just me)

Honnestly it's not that interesting discussing about me myself and I. I was
just trying to convey where some of the resentment was coming from.

Again, that's not the point. We think the Erlang way is better there. It's
that simple. I really hope Elixir folks can sleep at night thinking there
is a world with diverging views.

Ever better, we can coexist well.

Straight and simple, each time the erlang community rejects something from
Elixir, we are going to say Elixir is wrong on that topic. It's not mean.
There is no hard feeling. It's going too happen again. I sincerely hope we
can live with it.

Le lun. 25 avr. 2022 =C3=A0 17:33, =C5=81ukasz Niemier <[email protected]> =
a =C3=A9crit :

> > Most of us prefer Erlang and don't want Erlang to become Elixir, that i=
s
> all.
>
> But who is trying to make Erlang into Elixir? From what I see in this EEP
> it is mostly to make some stuff more explicit.
>
> > - Me: "Why. I'll be way faster in Erlang, that is what I know."
>
> Out of question, how it would be faster in Erlang? Because, you know, if
> that can be written in Erlang then it can be written in Elixir with no
> overhead.
>
> --
>
> =C5=81ukasz Niemier
> [email protected]
>
>

--000000000000f7f2bb05dd7c75a5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Experience. Over the years I have developed a workflow ar=
ound Erlang. So yes, I am faster in Erlang. To be clear, thee main reasons =
are :<div dir=3D"auto">- the way my text editor is configured</div><div dir=
=3D"auto">- the testing philosophy in elixir (which I find horrible but may=
be that&#39;s just me)</div><div dir=3D"auto"><br></div><div dir=3D"auto">H=
onnestly it&#39;s not that interesting discussing about me myself and I. I =
was just trying to convey where some of the resentment was coming from.</di=
v><div dir=3D"auto"><br></div><div dir=3D"auto">Again, that&#39;s not the p=
oint. We think the Erlang way is better there. It&#39;s that simple. I real=
ly hope Elixir folks can sleep at night thinking there is a world with dive=
rging views.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Ever better=
, we can coexist well.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"a=
uto">Straight and simple, each time the erlang community rejects something =
from Elixir, we are going to say Elixir is wrong on that topic. It&#39;s no=
t mean. There is no hard feeling. It&#39;s going too happen again. I sincer=
ely hope we can live with it.=C2=A0</div></div><br><div class=3D"gmail_quot=
e"><div dir=3D"ltr" class=3D"gmail_attr">Le lun. 25 avr. 2022 =C3=A0 17:33,=
 =C5=81ukasz Niemier &lt;<a href=3D"mailto:[email protected]">lukasz@niemie=
r.pl</a>&gt; a =C3=A9crit=C2=A0:<br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">&g=
t; Most of us prefer Erlang and don&#39;t want Erlang to become Elixir, tha=
t is all.<br>
<br>
But who is trying to make Erlang into Elixir? From what I see in this EEP i=
t is mostly to make some stuff more explicit.<br>
<br>
&gt; - Me: &quot;Why. I&#39;ll be way faster in Erlang, that is what I know=
.&quot;<br>
<br>
Out of question, how it would be faster in Erlang? Because, you know, if th=
at can be written in Erlang then it can be written in Elixir with no overhe=
ad.<br>
<br>
--<br>
<br>
=C5=81ukasz Niemier<br>
<a href=3D"mailto:[email protected]" target=3D"_blank" rel=3D"noreferrer">l=
[email protected]</a><br>
<br>
</blockquote></div>

--000000000000f7f2bb05dd7c75a5--