jurip

18 ms·

181.
by jurip 11y ago
Yeah, and Objective-C and now Swift inherited that same convention. Objective-C: [self frob:param1 withObject:param2]; Swift: self.frob(param1, withObject:param2)
182.
by jurip 11y ago
I've come to the conclusion that git got branches right. The idea of permanent metadata for branches is appealing, but repository-wide single namespace is bit of a PITA in some circumstance. Mercurial's bookmarks are the same as g
183.
by jurip 12y ago
At the moment, the only thing keeping 32 bit frameworks resident on my Mac is Dropbox. I'm sure there's plenty of legacy apps out there, but it looks to me like it's not that common anymore.
184.
by jurip 12y ago
It's been an obvious shortcoming for over 20 years, though. Maybe it'll get better some day, but at this point it's probably best not to count on it.
185.
by jurip 12y ago
That page doesn't mention blocks at all, though. Apple themselves use the (id value, NSError *error) completion block style with NSURLSession: https://developer.apple.com/library/ios/documentation/Founda.
186.
by jurip 12y ago
Yeah, that's really badly worded. What it's trying to say is that if a Cocoa method has a NSError parameter, it will indicate error state by nil/NO return value. It doesn't say anything about the value of the NSError
187.
by jurip 13y ago
That sounds like me. After that, I went OS/2. These days I fear for any platform I choose.
188.
by jurip 13y ago
Yeah, Node didn't exist. Python was over ten years old in 2003. In Python web development there had already been CGIs, mod_python and two major releases of Zope, with hope of Zope 3 on the horizon. Ruby is almost as old as Python.