thingsdoer

6 ms·

1.
Devops / server owners, what did you name your server(s) and why?
5 points by thingsdoer 10y ago|1 comments
2.
by thingsdoer 13y ago
Neat! Where did you get the data?
3.
Ask HN: What is the must have iOS book for the modern developer.
7 points by thingsdoer 13y ago|3 comments
4.
Show HN: miyagi, a novel obj-c JSON marshaller(github.com)
4 points by thingsdoer 13y ago|1 comments
5.
by thingsdoer 13y ago
That's an extreme edge case though, since if you're using a mutating method, you're using a mutating string, and you're probably aware of that.
6.
by thingsdoer 13y ago
>> hn.txt
7.
by thingsdoer 13y ago
The issue with the default syntax in NSString is that the mutating methods are the more concise, but are also the ones you use the least. It makes far more sense for the more used methods to be more concise than their mutating siblings. I d
8.
Show HN: miyagi, an obj-c JSON marshaller that doesn't suck to use.(github.com)
3 points by thingsdoer 13y ago|0 comments
9.
by thingsdoer 13y ago
-(NSString*)capitalizeInPlace; is the actual signature. The reasoning for this is for consistency, while still maintaining autocomplete proximity.
10.
by thingsdoer 13y ago
I'm not super comfortable with breaking message syntax like that. Also, very wary of using a #define with a short oft used keyword in a library that will be imported in majority of headers.
11.
by thingsdoer 13y ago
The problem people have with the format implementation is that no matter what you do, it's either obtuse shorthand, or incredibly verbose. The reality is, that NSString needs native formatting sugar. Anything else would really just be
12.
by thingsdoer 13y ago
There are already a lot of Ruby categories out there. ObjectiveSugar covers a lot of bases. I personally wouldn't import more Ruby categories. The NSString API is a weak point of Cocoa, IMO, but in general I wouldn't like to see a
13.
by thingsdoer 13y ago
Unfortunately, something like "fmt()" isn't really elegant enough, or "objective-c" enough.
14.
by thingsdoer 13y ago
Actually, I might add some protection around this specific case.
15.
by thingsdoer 13y ago
Still don't have a clever implementation.
16.
by thingsdoer 13y ago
I'd correct the category. Also, NSString is not going to change. If it does, it will be rewritten extensively, most probably obsoleting this category.
17.
Show HN: NSString + Ruby(github.com)
87 points by thingsdoer 13y ago|52 comments