Objective-C doesn't have namespaces (like C), so people use two-letter prefixes on their types to prevent name clashes. The NS prefix is used by Apple's Foundation and AppKit frameworks, that originated from NeXTSTEP, hence NS.
Yes, but it's not like this is some hidden legacy stuff, that you're not supposed to encounter. This is part of the public macOS API: <a href="https://developer.apple.com/documentation/appkit/nstext" rel="nofollow">https://developer.apple.com/documentation/appkit/nstext
Every AppKit and Foundation type uses the NS prefix, and will keep doing so for any foreseeable future. New NS types are added to these frameworks each macOS release.
Mission control is not supposed to print the name of the control/window visible to the user though, surely, which is what the article is talking about.
osdjeicjejcjjr · · focus · HN ↗
[dead]
[deleted] · · focus · HN ↗
[deleted]
robin_reala · · focus · HN ↗
meindnoch · · focus · HN ↗
Objective-C doesn't have namespaces (like C), so people use two-letter prefixes on their types to prevent name clashes. The NS prefix is used by Apple's Foundation and AppKit frameworks, that originated from NeXTSTEP, hence NS.
sedawkgrep · · focus · HN ↗
meindnoch · · focus · HN ↗
Every AppKit and Foundation type uses the NS prefix, and will keep doing so for any foreseeable future. New NS types are added to these frameworks each macOS release.
pixelesque · · focus · HN ↗
waffletower · · focus · HN ↗
Borgz · · focus · HN ↗
codepoet80 · · focus · HN ↗
osdjeicjejcjjr · · focus · HN ↗
there, just told you
runjake · · focus · HN ↗
Citation: I was a NeXTSTEP developer.
ChrisRR · · focus · HN ↗
sleepybrett · · focus · HN ↗