Starting with macOS Sierra, I noticed a performance issue caused by getting the hostname of the machine that TKE is run from. It seemed to take around 5 seconds or so to get this information from the operating system, which is much longer that one would expect it to take.

TKE uses this information in two places. First, the hostname is displayed in the title bar of the application window, just to the left of the current working directory information. Due to the performance issue that I was seeing, I decided in version 3.2 or 3.3 to remove this from the title bar. It is still gone for macOS users in the 3.4 stable release. The second place where TKE uses it is when normalizing a file pathname in cases where the filename could exist on a different NFS mounted drive. The current hostname is compared to the hostname of the file, and if it is different, the NFS mount information is used to normalize the file's pathname. This is unavoidable, unfortunately, which causes TKE's startup time on macOS to be slower than it should be.

Recently I found an article on the web that addresses this issue (https://apple.stackexchange.com/questions/175320/why-is-my-hostname-resolution-taking-so-long). Essentially, the solution for this problem is to set the HostName system configuration variable to that of the LocalHostName system configuration variable which can be accomplished with the following terminal command:

scutil --set HostName $(scutil --get LocalHostName)

Give this command a try and see if it helps improve TKE's startup time.