KZPlayground – Playgrounds for Objective-C (opens in new tab)

This is unfortunate for German, but not a big deal for most other-language speakers, I think. I could of course be off, but as an English-speaking American who's likely a bit more knowledgable about WWII than average, the unfortunateness of "NS" has never crossed my mind before and I'd have never even known about the issue with "KZ" if it hadn't been mentioned here.

Anyway, it seems an odd request to make of an apparently Polish person.

What makes it even worse is the name KZPlayground, for me personally stuff like that sends shivers down my spine, though I'm slightly biased (being Austrian, family history, etc.).

kz can thoug also be the TLD/country code for Kazakhstan, there are just a lot of ambiguities in all the human languages and product naming can be a real pain (some car-makers have some experience with especially bad naming :) )

I've been under the impression that Apple asks third parties to use three-letter prefixes (that's the default in Xcode when you start a new project).

Apple would like to keep two-letter prefixes for their own frameworks: CA for Core Animation, SK for SceneKit, etc.

The author should maybe consider renaming the project. The first thing that comes to my (german) mind when I hear KZ is concentration camp.

The documentation clearly states that it uses dyci: "KZPlayground is powered by Dyci code injection tool". This project is doing what open source is intended for - it uses existing tools to build new things.

This isn't a backport of the Xcode 6 Playground feature to Objective-C. It's an iPad view controller and glue code intended for the simulator; you add your own code and the view controller provides controls that correspond to Playground features.

A big part of Apple's Playgrounds is how it shows you the value produced by every line of code, shows how many times loops were executed, and allows you to view a complete history of the values any particular variable took on during a loop. This is hard to accomplish, as it requires modifying the compiler to output instrumented code (and it's also why Swift playgrounds don't execute very fast). This Objective-C version doesn't appear to do any of that. It looks great and that's not meant as criticism in any way, but it's not reasonable to take this and turn it into some Apple bashing.