3 ms·
It's 2013, why aren't you using properties in all of your classes? And you should be prefixing your classes to avoid namespace collisions.
by fyaqub 13y ago
It's 2013, why aren't you using properties in all of your classes? And you should be prefixing your classes to avoid namespace collisions.
- ux-app 13y ago> It's 2013, why aren't you using properties in all of your classes? It's snarky comments like these that prevent people from confidently sharing their code. Got a helpful comment to make? Great! How about sharing it minus the veiled insults next time? OP doesn't owe you clean code. Don't like the code? Don't use it.
- itafroma 13y ago> OP doesn't owe you clean code. Don't like the code? Don't use it. Or better yet, contribute a patch/PR. The OP's intention in sharing it was to get contributors: https://news.ycombinator.com/item?id=5678490 https://news.ycombinator.com/item?id=5678490
- fyaqub 13y agoHow is this a snarky comment? Properties were introduced in Objective-C 2.0 which is relatively new, thus, I'm asking why he chose not to use them when they're standard practice now. And prefixing classes is not for "clean code", it's to avoid namespace collisions which is a valid and common issue in Objective-C development.
- bennyg 13y agoI'll take these suggestions into account - I've also only been coding for about a year and a half, and graduated with an Art degree. I'm the ESL equivalent of programming.