Just popping in to add whatever context I can:

I assume this was a very macOS-centric feature that caused all JavaScript console.log()s to also add to the Apple System Log, for whichever developers might find that tooling desirable to use?

Logs an error message to the Apple System Log facility.

https://developer.apple.com/documentation/foundation/1395275-nslog

This is another home-grown Atom thing... https://github.com/atom/node-nslog

Given the many obscure problems this has caused, I'm pretty inclined to yeet and delete it.

Lite approve ✅ 👍, since I can't think of a strong technical basis on which to advocate for or against this. (Nor have I tested this change for breakage, either.) Anecdotally, nslog has caused nothing but pain and confusion, as far as I can recall anyway.

And I doubt that anyone takes advantage of this printing to the Apple System Log on their mac? Would be interested to hear from anyone who does, but it'd have to be a really important feature to justify the headaches it brings (on all platforms, especially Windows!) just for this minor, macOS-only feature.

Wonderful, @DeeDeeG. We can work like we did with i18n - we remove it, and if the removal causes problems/complains we re-add it later :)