While I like Swift (from what I've played with it, around SourceKitService crashing every two seconds), it doesn't provide you with the "just enough rope" that Objective-C does. Many of Objective-C's best capabilities lie in its ability to do some crazy things with metaprogramming (much like Ruby). This is a terrific introduction to that. I'd love to see a full-on book dedicated to the subject, TBH.
As an aside, I can't say I've ever seen these Genius annotations in a blog post before, but the way they're used here make this read like a chapter from a textbook with really useful sidebars. I hope this sort of thing catches on with other development blogs.
When I worked for Universal Uclick, we released the GoComics app all at the same time for iOS, Android, and Windows Phone. I worked on the iOS release until its launch, and we had the ear of its developer support team up until and well after its release. We even were able to get the app 'featured' in the App Store shortly after its release.
We didn't experience a cold shoulder at all from Apple after putting out the app for other platforms. But then again, that was just us.
DHH is reporting that criminals are bringing down the Basecamp network of sites in a blackmail attempt. A working writeup is on a gist from DHH right here: https://gist.github.com/dhh/9741477
I'm beginning to appreciate the concept of Interactors and Entities more these days (application-specific business logic versus application-independent business logic), now that I'm some sort of a mature adult (jury is still out on that one). This post highlights that as part of the "VIPER"-style architecture. The great part about these patterns is that they can typically be applied to a lot of modern Ruby and iOS projects _both_ to cleanup code.
Great post; I always enjoy reading these sorts of things.
Granted, to each their own, but the one thing I concern myself with is readability and learning curve, especially on projects where there's even the remotest possibility that somebody could be inheriting my code. If I toss in a library like ReactiveCocoa, that's an incredibly steep learning curve that a developer will have to master in addition to any other curve presented by Cocoa Touch / Foundation / Core Data / whatever's already there.
The argument could be made for lots of other Objective-C libraries and frameworks, I suppose, but ReactiveCocoa doesn't seem to offer more in benefits than what it costs to learn it.
Kudos to Mattt Thompson and the whole community of collaborators that put work into this release. AFNetworking makes a large part of my job making iOS apps a joy, and I can't wait to start working with latest round of changes and features in this new release (including support for NSURLSession in iOS 7).
That said if you haven't used AFNetworking before, I highly recommend doing so. Start with the AFHTTPRequestOperation class(es). And if you're writing an API wrapper of any kind, definitely check out subclassing either AFHTTPRequestOperationManager (for iOS 6) or AFHTTPSessionManager (for iOS 7).
Edit: Derp, I was wrong — AFHTTPClient's been split-up. Thanks for calling me out, @dcaunt; I've updated my remarks.
Another person trying to make this a "Hacker News vs. Reddit" thing, which still doesn't appeal to the reason sectors of my brain. Definitely not a ripoff; Mashable's clearly grasping at straws again.
Split panes is pretty much the main reason I need iTerm2. That, combined with system-wide hotkey toggling (which I used to get on Terminal with Visor), and Send Commands to All Sessions mode (cmd-ctrl-i, I think) makes me a happy command liner.
I'm with thwarted on this one. I don't want to put my repo on a service where I have to opt-out of things based on extraneous files in my repo. That's extra clutter in my repo for something that could easily be handled in other ways (not to mention the fact that repos would be opted-in by default).
I can't stress enough how important it is to _not_ use `and` and `or`. As a former die-hard fan of those operators, it bit me in the ass so hard when those didn't exactly work the way they were supposed to. I've been using && and || now for years and I haven't looked back. /PSA
Andrews McMeel Universal / Universal Uclick, Kansas City, MO, looking for a full-time software engineer.
We're an awesome, closely-knit tech department with a core web / design / scripting / app development group of 7 people, looking for an 8th. We work on websites like GoComics.com, Dilbert.com, Doonesbury.com, and ThePuzzleSociety.com. As you may have deduced, we're a comic and editorial syndicate with focuses on both B-to-B and B-to-C channels. We own syndication rights to Dilbert, Peanuts, Calvin & Hobbes, Garfield, FoxTrot, and tons more.
You gotta know your POSIX/UNIX environment, you gotta love building and scaling websites, and you gotta love learning and incorporating new things. We use a lot of Ruby and Perl, along with some Java, Node, and Objective-C.
The Xbox never was an open platform to begin with, unlike the PC. The PC has never been the kind of platform to lock stuff down; while Microsoft may have their merits for doing so, a lot of people are up in arms about it and rightly so (as the PC is so widely distributed).
Plus, while Mojang did license and partner the code with another firm for the Xbox port, they didn't create it directly themselves.
Thank you (x3) for the explanation on how this works and what went wrong. Your comment alone is more insightful on any of these articles that've been submitted on this problem. You win my Internets, mitchellh.