Re: CEDET, future and Emacs
Fermin <[email protected]> Sun, 28 Mar 2021 19:59:29 +0200
| Newsgroups | gmane.emacs.cedet |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============2091394483854295537== Content-Type: multipart/alternative; boundary="------------DCDC4AF8928F58AA83D5150A" Content-Language: en-US This is a multi-part message in MIME format. --------------DCDC4AF8928F58AA83D5150A Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit You are right, keeping up with new languages is quite hard, I think this is why CEDET need more people involve, we can never match the level of adoption of LSP, but we can provide a decent programming experience for a variety of languages. Focusing on a balance between popular (to attract users) and stable (languages that don't require a lot of changes over time) can be an interesting strategy, I'm not saying to focus all the energy into writing a javascript production parser or a Ada parser, something in between, that can be stable enough and popular enough. For now, I think improving the actual parsing infrastructure is more critical that supporting new languages, giving the synchronous nature of CEDET, right now is not well suited for large projects, Emacs now support (partially, and in a hackish way) asynchronous processing <https://elpa.gnu.org/packages/async.html>, and I hope in the near future, with native compilation <https://www.emacswiki.org/emacs/GccEmacs>, the elisp performance can improve drastically ,which can really play really well if CEDET is prepared to take advantage of this changes. On 28/03/2021 19:13, Alex Ott wrote: > Imho, LSP is still required - it's quite hard to build grammars for > multiple languages, and maintain them as languages evolve... > > On Sun, Mar 28, 2021 at 6:15 PM Pankaj Jangid <[email protected] > <mailto:[email protected]>> wrote: > > Vladimir Nikishkin <[email protected] > <mailto:[email protected]>> writes: > > > Things are actually moving (albeit not super fast), just not > inside the SF > > repo. Since cedet was merged into the main emacs tree, you need > to grep > > emacs' git log, not sf repos. > > Yup. Just saw one more commit today. I build emacs-master daily for my > personal use. > > By "not moving" I meant that the expectations are high. Things > like LSP > would not be required if CEDET is seriously taken care of. > > > > > _______________________________________________ > Cedet-devel mailing list > [email protected] > <mailto:[email protected]> > https://lists.sourceforge.net/lists/listinfo/cedet-devel > <https://lists.sourceforge.net/lists/listinfo/cedet-devel> > > > > -- > With best wishes, Alex Ott > http://alexott.net/ <http://alexott.net/> > Twitter: alexott_en (English), alexott (Russian) > > > _______________________________________________ > Cedet-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/cedet-devel --------------DCDC4AF8928F58AA83D5150A Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <p>You are right, keeping up with new languages is quite hard, I think this is why CEDET need more people involve, we can never match<br> the level of adoption of LSP, but we can provide a decent programming experience for a variety of languages.</p> <p>Focusing on a balance between popular (to attract users) and stable (languages that don't require a lot of changes over time) can be<br> an interesting strategy, I'm not saying to focus all the energy into writing a javascript production parser or a Ada parser, something in<br> between, that can be stable enough and popular enough.</p> <p>For now, I think improving the actual parsing infrastructure is more critical that supporting new languages, giving the synchronous nature<br> of CEDET, right now is not well suited for large projects, Emacs now support (partially, and in a hackish way) <a moz-do-not-send="true" href="https://elpa.gnu.org/packages/async.html">asynchronous processing</a>, <br> and I hope in the near future, with <a moz-do-not-send="true" href="https://www.emacswiki.org/emacs/GccEmacs">native compilation</a>, the elisp performance can improve drastically ,which can really play really well if CEDET is prepared to take advantage of this changes.</p> <p><br> </p> <br> <div class="moz-cite-prefix">On 28/03/2021 19:13, Alex Ott wrote:<br> </div> <blockquote type="cite" cite="mid:CALV1_=LN=0Bw3a8rUKiQa9+PKtMwbah-TePthkMHoQh2EG4vCg@mail.gmail.com"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> <div dir="ltr">Imho, LSP is still required - it's quite hard to build grammars for multiple languages, and maintain them as languages evolve...<br> </div> <br> <div class="gmail_quote"> <div dir="ltr" class="gmail_attr">On Sun, Mar 28, 2021 at 6:15 PM Pankaj Jangid <<a href="mailto:[email protected]" moz-do-not-send="true">[email protected]</a>> wrote:<br> </div> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Vladimir Nikishkin <<a href="mailto:[email protected]" target="_blank" moz-do-not-send="true">[email protected]</a>> writes:<br> <br> > Things are actually moving (albeit not super fast), just not inside the SF<br> > repo. Since cedet was merged into the main emacs tree, you need to grep<br> > emacs' git log, not sf repos.<br> <br> Yup. Just saw one more commit today. I build emacs-master daily for my<br> personal use.<br> <br> By "not moving" I meant that the expectations are high. Things like LSP<br> would not be required if CEDET is seriously taken care of.<br> <br> <br> <br> <br> _______________________________________________<br> Cedet-devel mailing list<br> <a href="mailto:[email protected]" target="_blank" moz-do-not-send="true">[email protected]</a><br> <a href="https://lists.sourceforge.net/lists/listinfo/cedet-devel" rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.sourceforge.net/lists/listinfo/cedet-devel</a><br> </blockquote> </div> <br clear="all"> <br> -- <br> <div dir="ltr" class="gmail_signature"> <div dir="ltr"> <div>With best wishes, Alex Ott<br> <a href="http://alexott.net/" target="_blank" moz-do-not-send="true">http://alexott.net/</a><br> Twitter: alexott_en (English), alexott (Russian)<br> </div> </div> </div> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <pre class="moz-quote-pre" wrap="">_______________________________________________ Cedet-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/cedet-devel">https://lists.sourceforge.net/lists/listinfo/cedet-devel</a> </pre> </blockquote> </body> </html> --------------DCDC4AF8928F58AA83D5150A-- --===============2091394483854295537== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============2091394483854295537== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Cedet-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cedet-devel --===============2091394483854295537==--