It is because this is that offensive to anyone who writes objective-c for a living. Really? I write objective-c for a living and I'm not finding it offensive a

It is because this is that offensive to anyone who writes objective-c for a living. Really? I write objective-c for a living and I'm not finding it offensive at all. I may not agree with all of it, but rather than getting upset about it I'm trying to understand where this developer is coming from. They clearly put effort into making it, so I'll give them the benefit of the doubt that there must be some gains to be had here. This is all kinds of wrong. Is it correct from the language specification's point of view? Does the compiler allow it? Does it generate correct bytecode? It seems it might not align with your code style or even widely accepted "best practices" but it's probably not all kinds of wrong. That level of rigor might be appropriate for certain environments (health care, flight control, etc) but not all software needs to be held to that standard. The reaction in this thread seems awfully similar to The Great Javascript Semicolon Wars that took place earlier this year. [Y]ou must consider how it fits into that surrounding code. Perhaps this library is meant to shift the way that new code is written. Maybe it'll get some of those bazillion smart people working on other libraries to see a different way to do things. Relax. Don't get upset. It's not meant as an affront to your style or sensibilities. Consider this by @fat [1]: Projects with the most radically unique styles often have the highest internal standards for code quality and consistency. People put so much thought into the written code itself that it actually engenders a new sort of pride. [1]: Eating a whopper: http://byfat.xxx/eating-a-whopper http://byfat.xxx/eating-a-whopper