brentsimmons
brentsimmons

For some unknown reason, Swift protocol names ending in “ing” are like nails on chalkboard to me. I know the API design guidelines say it’s okay, but I still feel a little ill whenever I see one of these names.

|
Embed
Progress spinner
jeffmerola@mastodon.social
jeffmerola@mastodon.social

@brentsimmons just swift? Or does NSCoding bother you too?

|
Embed
Progress spinner
In reply to
brentsimmons
brentsimmons

@jeffmerola I think that I'm just used to NSCoding because it's been around so long. But, to answer your question, ing suffixes bother me in Objective-C too. (I just didn't mention it because people don't write much ObjC any more.)

|
Embed
Progress spinner
heyscottyj
heyscottyj

@brentsimmons API.offend.ing? I’ll show myself out.

|
Embed
Progress spinner
nicklockwood@mastodon.social
nicklockwood@mastodon.social

@brentsimmons same. It's one of those things that feels like it was transplanted from a horrible enterprise-y languages like Java.

|
Embed
Progress spinner
indigo@techhub.social
indigo@techhub.social

@brentsimmons Not a fan either. I guess the only thing they have going for them is that you end up with simple and consistent naming convention across entire team even if it’s a large organisation.

|
Embed
Progress spinner