build-emacs-for-macos VS dotfiles

I built emacs from source, native comp, a few months ago and recently heard about pgtk. Is this worth it (for more smoothness, better user experience) on MacOS? I saw this thread: https://github.com/jimeh/build-emacs-for-macos/issues/45 where it was mentioned that you have to turn off the MacOS specific flag, so I’m not sure if it’s more harm than good, and what benefit it may serve. Anyone have experience optimizing their emacs on MacOS as much as possible? I basically run native comp vanilla emacs with only about 100 lines in my init file, which I byte compile (I’m not sure if the init file byte compilation helps? It seems like even though packages get compiled down natively, going into the native code folder (alongside byte compilations) , init.el doesn’t have an option for it).

Details about the helper is in the readme here, and source for the helper is here.

I've been stuck on a build from February 23rd, I think, because all other builds since then have had some instability or funny quirks. Just built this today from source (thank you build-emacs-for-macos) and it's been solid so far!

Hi fellows, I am using this repo to build emacs on aarch64 mac. During the building, there are a lot of warning messages like:

I recognized your avatar. You're the one behind https://github.com/jimeh/build-emacs-for-macos . Nice project, I am using it to produce the macOS binary.

update: tried this build script and seems good

https://github.com/jimeh/build-emacs-for-macos

I've been using this: https://github.com/jimeh/build-emacs-for-macos

I use https://github.com/jimeh/build-emacs-for-macos which makes the custom build really easy.

Alternatively if you prefer to compile Emacs on your machine, there’s emacs-plus and my own build-emacs-for-macos which both have options to enable native compilation for 28.x and later builds.

I would recommend building from source like this for MacOS nowadays: https://github.com/jimeh/build-emacs-for-macos

(taken from https://github.com/siraben/dotfiles/blob/master/home-manager/.config/nixpkgs/python-packages.nix) but that did not even download the packages in question.

I had the exact same kernel parameters in my NixOS configuration[0] and after some benchmarks (mostly Emacs-related) I observed a 10-15% speedup, pretty neat.

[0] https://github.com/siraben/dotfiles/commit/c0eb0b43083738cab...

Note that when you use LSP with Emacs, installing language servers can quickly lead to dependency hell. I use home-manager[0] to specify which language servers I want installed[1] (among other things such as compilers for different languages) so integration with Emacs is reproducible.

[0] https://github.com/nix-community/home-manager

[1] https://github.com/siraben/dotfiles/blob/bad2e8a29b6622e10bc...

Using Nix and home-manager I'm able to have this setup with Emacs work across Linux and macOS (x86 and arm64) because it compiles the grammars from Nixpkgs itself (the grammar list can also be augmented declaratively with other grammars).

[0] https://github.com/siraben/dotfiles/blob/a0f49781ecb05693908...

I recently got into running my own NixOS server—setting up Nextcloud[0], a website[1], DNS server and most recently a mail server[2] were all incredibly easy, in fact, setting up DNS records is more involved than configuring a mail server on NixOS! This was all done on a server with less than 10 GB of disk space as well.

With additional software such as NixOps, personal servers can also be easily spun up and provisioned.

While inevitably there are rough edges if you look deeply enough, I think the default OOTB experience has been incredible for use on a server and as a day-to-day distro. Highly predictable and declarative configurations is the way to go.

[0] https://github.com/siraben/dotfiles/blob/ffaaacf8888a5c4167b...

[1] https://siraben.dev

[2] https://gitlab.com/simple-nixos-mailserver/nixos-mailserver