Re: [Erlang Forums] [Erlang/OTP Proposals/Proposals: RFC] Re-visiting EEP-0055
Michael Malter <[email protected]> Mon, 25 Apr 2022 08:13:14 +0200
| Newsgroups | gmane.comp.lang.erlang.general |
|---|---|
| Message-ID | <CADE9FeGO-V6dFeu-9nB358X6HJFEugT6nUYr1VSZ_Nvt6y4aBg@mail.gmail.com> |
--0000000000006f739405dd747979 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I said it for years. Elixir is cutting the branch it is sitting on. Oh well, we will be fine for quite a few years. I haven't read the whole thing, it is quite difficult to digest but I am not sure anyone mentioned that sigils are hard to read. It's bad in ruby, horrible in perl. I am not sure why we are taking ideas from these languages. I mean, I actually enjoy writing ruby but just fail to see where it stands in a prology context. Little funny story on the side. I go to a local erlang meetup, the topic of the day is "Discovering erlang" or something similar. An organizer litteraly shouted on me just for mentionning erlang. The whole thing revolved around selling elixir products. I'll let you imagine the atmosphere in the room, full of begginers. One (courageous ? ) guy left on the spot. We all wished the coexistence would be peaceful and productive. It certainly was for the most part. But let's face it we are more and more dealing with monkey crusaders. Consultants also. If I have an economic incentive to tell you that making a pabx in fortran is great, I'll just tell you that. This proposal reeks of "Erlang does not look like what I am used to, so let's make it user friendly". Le lun. 25 avr. 2022 =C3=A0 07:41, Eric Pailleau <[email protected]>= a =C3=A9crit : > Yes, this 'pinning operator' will just pin erlang in the extinct species > museum. > > Envoy=C3=A9 depuis mon mobile > > > ---- zxq9 a =C3=A9crit ---- > > From the EEP, which is about "pinning operators" (will the nonsense > > cease?): > > > In Erlang, they would be optional > > > > So why would you even want this? The entire idea is stupid, *implies* a > > break with the basic rules already built into the language, and appears > > to be nothing more than a way to roadmap the destruction of Erlang over > > time with gee-whiz glyphy syntax of the sort which Erlang has been thus > > far generally free. > > > > That's a big "NO" from me on this EEP, but I imagine anyone could have > > already guessed that. Thanks for the heads up. I don't expect sanity to > > prevail over time -- it is just the trend of the times -- but it was > > interesting to at least see this mentioned to those of us still > > subscribed to the bad dirty old ML. > > > > -Craig > > > > On 2022/04/21 21:32, Leonard Boyce wrote: > > > I'm copying the Erlang Questions ML with this post since there was > > > significant and heated discussion regarding this EEP and not all ML > > > subscribers have joined the forum. > > > > > > On Wed, Apr 20, 2022 at 10:20 PM Bryan Paxton via Erlang Forums > > > <[email protected]> wrote: > > >> > > >> starbelly EEF Board > > >> April 21 > > >> > > >> EEP-0055 (https://github.com/erlang/eep/blob/master/eeps/eep-0055.md) > was submitted on > > >> 21-Dec-2020. > > >> > > >> An accompanying implementation (https://github.com/erlang/otp/pull/295= 1) > was submitted in which a lot of conversation ensued. > > >> > > >> It was decided that the EEP would not be set for inclusion in OTP-24, > per the time table at that juncture and that it would be revisited prior = to > OTP-25. OTP-25 is now at a point where this is not possible. > > >> > > >> That said, I wanted to start a topic here about the EEP and gun for > inclusion in OTP-26. > > >> > > >> I would point to @kennethL=E2=80=99s last comment ( > https://github.com/erlang/otp/pull/2951#issuecomment-770878570) on the PR > as a starting point for discussion. > > >> > > >> I suppose my overarching question here is : Is this still on the table= ? > And if so, what are the road blocks? Kenneth pointed out some possible > roadblacks that needed investigation, but it=E2=80=99s not clear to me wh= at > happened after that. > > >> > > >> Of course, since I=E2=80=99m raising this topic, I=E2=80=99m obviously= in favor of the > operator I=E2=80=99d also be happy to work to drive it forward. > > >> > > >> ________________________________ > > >> > > >> Visit Topic or reply to this email to respond. > > >> > > >> You are receiving this because you enabled mailing list mode. > > >> > > >> To unsubscribe from these emails, click here. > > >> > > >> > > --0000000000006f739405dd747979 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto"><div dir=3D"auto">I said it for years. Elixir is cutting = the branch it is sitting on.</div><div dir=3D"auto"><br></div><div dir=3D"a= uto">Oh well, we will be fine for quite a few years.</div><div dir=3D"auto"= ><br></div><div dir=3D"auto">I haven't read the whole thing, it is quit= e difficult to digest but I am not sure anyone mentioned that sigils are ha= rd to read. It's bad in ruby, horrible in perl. I am not sure why we ar= e taking ideas from these languages. I mean, I actually enjoy writing ruby = but just fail to see where it stands in a prology context.</div><div dir=3D= "auto"><br></div><div dir=3D"auto"><br></div><div dir=3D"auto">Little funny= story on the side. I go to a local erlang meetup, the topic of the day is = "Discovering erlang" or something similar. An organizer litteraly= shouted on me just for mentionning erlang. The whole thing revolved around= selling elixir products. I'll let you imagine the atmosphere in the ro= om, full of begginers. One (courageous ? ) guy left on the spot.</div><div = dir=3D"auto">=C2=A0</div><div dir=3D"auto">We all wished the coexistence wo= uld be peaceful and productive. It certainly was for the most part. But let= 's face it we are more and more dealing with monkey crusaders. Consulta= nts also. If I have an economic incentive to tell you that making a pabx in= fortran is great, I'll just tell you that.=C2=A0</div><div dir=3D"auto= "><br></div><div dir=3D"auto">This proposal reeks of "Erlang does not = look like what I am used to, so let's make it user friendly".</div= ></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr"= >Le lun. 25 avr. 2022 =C3=A0 07:41, Eric Pailleau <<a href=3D"mailto:eri= [email protected]">[email protected]</a>> a =C3=A9crit=C2=A0:= <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord= er-left:1px #ccc solid;padding-left:1ex"><p dir=3D"ltr" style=3D"margin-top= :0;margin-bottom:0">Yes, this 'pinning operator' will just pin erla= ng in the extinct species museum.</p> <br> <p dir=3D"ltr" style=3D"margin-top:0;margin-bottom:0">Envoy=C3=A9 depuis mo= n mobile </p><br><br>---- zxq9 a =C3=A9crit ----<br><br> From the EEP, whic= h is about "pinning operators" (will the nonsense<br><br>cease?):= <br><br> > In Erlang, they would be optional<br><br><br><br>So why would= you even want this? The entire idea is stupid, *implies* a<br><br>break wi= th the basic rules already built into the language, and appears<br><br>to b= e nothing more than a way to roadmap the destruction of Erlang over<br><br>= time with gee-whiz glyphy syntax of the sort which Erlang has been thus<br>= <br>far generally free.<br><br><br><br>That's a big "NO" from= me on this EEP, but I imagine anyone could have<br><br>already guessed tha= t. Thanks for the heads up. I don't expect sanity to<br><br>prevail ove= r time -- it is just the trend of the times -- but it was<br><br>interestin= g to at least see this mentioned to those of us still<br><br>subscribed to = the bad dirty old ML.<br><br><br><br>-Craig<br><br><br><br>On 2022/04/21 21= :32, Leonard Boyce wrote:<br><br>> I'm copying the Erlang Questions = ML with this post since there was<br><br>> significant and heated discus= sion regarding this EEP and not all ML<br><br>> subscribers have joined = the forum.<br><br>> <br><br>> On Wed, Apr 20, 2022 at 10:20 PM Bryan = Paxton via Erlang Forums<br><br>> <<a href=3D"mailto:noreply@erlangfo= rums.com" target=3D"_blank" rel=3D"noreferrer">[email protected]</a>= > wrote:<br><br>>><br><br>>> starbelly EEF Board<br><br>>= > April 21<br><br>>><br><br>>> EEP-0055 (<a href=3D"https://= github.com/erlang/eep/blob/master/eeps/eep-0055.md" target=3D"_blank" rel= =3D"noreferrer">https://github.com/erlang/eep/blob/master/eeps/eep-0055.md<= /a>) was submitted on<br><br>>> 21-Dec-2020.<br><br>>><br><br>&= gt;> An accompanying implementation (<a href=3D"https://github.com/erlan= g/otp/pull/2951" target=3D"_blank" rel=3D"noreferrer">https://github.com/er= lang/otp/pull/2951</a>) was submitted in which a lot of conversation ensued= .<br><br>>><br><br>>> It was decided that the EEP would not be = set for inclusion in OTP-24, per the time table at that juncture and that i= t would be revisited prior to OTP-25. OTP-25 is now at a point where this i= s not possible.<br><br>>><br><br>>> That said, I wanted to star= t a topic here about the EEP and gun for inclusion in OTP-26.<br><br>>&g= t;<br><br>>> I would point to @kennethL=E2=80=99s last comment (<a hr= ef=3D"https://github.com/erlang/otp/pull/2951#issuecomment-770878570" targe= t=3D"_blank" rel=3D"noreferrer">https://github.com/erlang/otp/pull/2951#iss= uecomment-770878570</a>) on the PR as a starting point for discussion.<br><= br>>><br><br>>> I suppose my overarching question here is : Is = this still on the table? And if so, what are the road blocks? Kenneth point= ed out some possible roadblacks that needed investigation, but it=E2=80=99s= not clear to me what happened after that.<br><br>>><br><br>>> = Of course, since I=E2=80=99m raising this topic, I=E2=80=99m obviously in f= avor of the operator I=E2=80=99d also be happy to work to drive it forward.= <br><br>>><br><br>>> ________________________________<br><br>&g= t;><br><br>>> Visit Topic or reply to this email to respond.<br><b= r>>><br><br>>> You are receiving this because you enabled maili= ng list mode.<br><br>>><br><br>>> To unsubscribe from these ema= ils, click here.<br><br>>><br><br>>><br><br></blockquote></div> --0000000000006f739405dd747979--