4 ms·

It is because this is that offensive to anyone who writes objective-c for a living. First of all, you are using properties to fake dot syntax for method calls.

by jawngee 14y ago

It is because this is that offensive to anyone who writes objective-c for a living. First of all, you are using properties to fake dot syntax for method calls. This is all kinds of wrong. Second of all, you are shortening the names of types because you are too lazy to type the first letter and hit space. This is beyond wrong. It's not the functionality, it's the implementation. And when writing libraries for others to use, you must consider how it fits into that surrounding code. There are a bazillion smart people working at Apple writing objective-c libraries. Have you seen anything like this? You think maybe there is a reason for that? Its just plain lazy, its just plain offensive. Learn objective-c. It's not that hard. Stop putting in all this work to produce something to fit this idea you can get around your weird perceptions of it and to shoehorn it into what you already know. Like I said in another post, it's sad because there seems to be a lot of work put into this.

jmduke 14y ago
It is because this is that offensive to anyone who writes objective-c for a living. I think you need to seriously stop and consider what should and should not offend you, and what is worthy and unworthy of such vitriol.
sticks 14y ago
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
mikeash 14y ago
"It is because this is that offensive to anyone who writes objective-c for a living." Please don't pretend you speak for other people, since it's pretty clear that you don't. Speak for yourself about how you dislike it as much as you want, but don't try to pretend that you have me or other people like me on your side when you don't.

by jawngee 14y ago

jmduke 14y ago

It is because this is that offensive to anyone who writes objective-c for a living. I think you need to seriously stop and consider what should and should not offend you, and what is worthy and unworthy of such vitriol.

sticks 14y ago

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

mikeash 14y ago

"It is because this is that offensive to anyone who writes objective-c for a living." Please don't pretend you speak for other people, since it's pretty clear that you don't. Speak for yourself about how you dislike it as much as you want, but don't try to pretend that you have me or other people like me on your side when you don't.