<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div><blockquote type="cite"><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);">Well known acronym capitalization is pervasive in Cocoa APIs and as a result it enables fast and easy comprehension and writing a good quality code.</span></font></blockquote></div><div><br></div><div>I could reply "they are confusing because they look like class names and clearly cause a higher number of errors in code." </div><div><br></div><div>My *actual* view is that both forms cause problems, so it doesn't much matter which we go with. </div><div><br><div>Sent from my iPhone</div></div><div><br>On May 19, 2016, at 1:30 PM, Pavel Kapinos <<a href="mailto:kapinos@twobytesoftware.com">kapinos@twobytesoftware.com</a>> wrote:<br><br></div><blockquote type="cite"><div><span>Hi Charles,</span><br><span></span><br><span>Thank you for your feedback! But we are not talking here bad or good names per se. Well known acronym capitalization is pervasive in Cocoa APIs and as a result it enables fast and easy comprehension and writing a good quality code. IMO it is quite important for future preservation in Swift 3. Have a good day!</span><br><span></span><br><span>Cheers,</span><br><span>Pavel.</span><br><span></span><br><blockquote type="cite"><span>On May 19, 2016, at 1:20 PM, <a href="mailto:charles@charlesism.com">charles@charlesism.com</a> <<a href="mailto:charlesism.com@gmail.com">charlesism.com@gmail.com</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I don't believe there's a correct answer here. Both urlHandler and URLHandler are bad names (for instances). Since we're stuck with camelCase, bad names are a fact of life.</span><br></blockquote></div></blockquote></body></html>