Bringing GNU Emacs to native code [video] • Hacker News Board

Re: Bringing GNU Emacs to native code [video]

#81

Post by bjoli » Tue, May 05, 2020, 10:53 AM UTC

rurban wrote: post #46

bjoli wrote: post #19

Earlier quoted context omitted.

Guile (the VM) runs elisp just fine. There has been zero optimization work done though so it is quite slow. The reason they did not go with guile was more political than anything else. It was also understandable from their point of view (and I say this as a guile weenie)

No, the reason is still slow string buffers. Politically everybody wants emacs to switch to guile.

Iirc Guile-emacs relies on Emacs for all string related functionality. The overhead comes for dynamic bindings that are currently slower in guiles elisp implementation. I haven't looked into it since talking to Robin about it in 2016.

You maybe have some more inside info, but back in 2016 I remember a lot of complaints and that guile was a liability for the much bigger Emacs project. Maybe even people threatening to retire as maintainers

Re: Bringing GNU Emacs to native code [video]

#82

Post by cion » Tue, May 05, 2020, 1:45 PM UTC

disgruntledphd2 wrote: post #80

pmiller2 wrote: post #58

Earlier quoted context omitted.

I'd recognize a LaTeX beamer presentation anywhere. Here is the corresponding paper: https://arxiv.org/pdf/2004.02504.pdf

From org-mode too, as it has the pointless Outline page that org always inserts into beamer presentations.

It's not pointless, but the outline only shows up if the generated tex file is compiled twice. The default org to latex export will only compile it once.

Alternatively, it is easy to suppress the outline slide altogether (add "toc:nil" to "#+OPTIONS:").

Re: Bringing GNU Emacs to native code [video]

#83

Post by hvis » Tue, May 05, 2020, 10:54 PM UTC

armitron wrote: post #70

hvis wrote: post #47

Earlier quoted context omitted.

Meaning, it's only really slow on macOS.

Multiple versions of macOS. And Windows. And possibly other less known systems. Besides, why would a discerning engineer put up with magit creating all these wasteful processes knowing that most of them are redundant, regardless of performance feel? If I was a magit developer, I would surely try to fix this.

On Windows it's not as fast as Linux, but it's not terrible either (as far as I heard).

Also see https://stackoverflow.com/a/16902730/615245 (I think it's not needed with the latest versions of Git anymore, though).

> If I was a magit developer, I would surely try to fix this.

Since you're just a regular user, did you check out the issue tracker for related discussions?

Re: Bringing GNU Emacs to native code [video]

#84

Post by disgruntledphd2 » Wed, May 06, 2020, 9:14 AM UTC

cion wrote: post #82

disgruntledphd2 wrote: post #80

Earlier quoted context omitted.

From org-mode too, as it has the pointless Outline page that org always inserts into beamer presentations.

It's not pointless, but the outline only shows up if the generated tex file is compiled twice. The default org to latex export will only compile it once. Alternatively, it is easy to suppress the outline slide altogether (add "toc:nil" to "#+OPTIONS:").

Oh I know. I have toc:nil as my default because it annoys me.

It's just a bit of a giveaway as to how the file was made.