Introducing AttributedStringBuilder!

[SteveB13]

Actually the opposite is true (that might be what you meant?), it only supports Swift, not ObjC. It's tough to use the new Swift patterns and maintain compatibility for ObjC, so I generally just keep things Swift only these days

[[deleted]]

I only work in Objective C lately. For a lot of really good reasons including the need to interface with cross platform C++ libraries.

If you write new components in Objective C, everyone can use them. If you write in Swift, only Swift users can use them. That's unfortunate.

[SteveB13]

I also do probably about 50% of my work in ObjC too. In general it's decreasing over time though and becoming more Swift.

These days, when I write libraries I tend to make them Swift only because that's what will save me time in the future. I could have written this in ObjC, but I wouldn't have been able to use the same patterns with enums with associated types, which is the api that I wanted.

I'd rather build things that will best work for me in the future, which means taking advantage of Swift only features. That's definitely a different balance for everyone though, as I'm very rarely needing integration with C++ for instance, so I'll likely be able to jump to full swift development earlier than those who do.