HNHacker News
TopNewBestAskShowJobs

smithclay

282 karma · joined June 29, 2012

doing tech things in san francisco
submissionscomments
smithclay··on IncludeOS: Run your C++ code directly on virtual hardware
There's also a JavaScript unikernel project: http://runtimejs.org/
smithclay··on Libraries Used in the Top 100 iOS Apps
Couple of companies come to mind:

* Realm.io has successfully positioned themselves as a thought leader in swift development for iOS by producing solid blog content and leading the Swift SF meetups (+ contributing to open-source projects).

* Crashlytics/Fabric.io is more interesting -- my experience with them has been entirely word-of-mouth (but they have a big presence at Twitter's developer conference/WWDC/Google IO, too).

* Parse generally has interesting, high-quality technical blog content: (https://blog.parse.com).

smithclay··on Libraries Used in the Top 100 iOS Apps
Anyone done any analysis on what top 100 apps are using Swift?

Similar to the cocoapods note, my guess is it's catching on much faster with the long tail than the most popular apps.

smithclay··on Should you use interface builder?
I'd add there's a huge advantage to using storyboards (especially with storyboard references) if you have a savvy UI Designer on the team who is comfortable using Xcode.

Under ideal circumstances, storyboards can allow non-iOS engineers to make substantial contributions to the UI and rapidly prototype new things.

smithclay··on Comprehensive diff between the Swift 1.2 and 2.0 standard libraries
Output generated from Xcode 6.4 and 7.0:

(echo "import Swift"; echo ":print_module Swift") | xcrun swift -deprecated-integrated-repl | open -f

http://ericasadun.com/2015/09/01/fetching-stdlib-declaration...

smithclay··on Security concerns with minified JavaScript code
Another reason is that minified code + gzipped code is expected for third-party JavaScript widgets (social media buttons, in-app chat, ads, etc) because of legitimate developer concerns around page-size bloat.
smithclay··on Swift 1.2 and Xcode 6.3 beta
The nested if-let statements of doom have been one of my major annoyances -- so glad to hear unwrapping multiple optionals in a single line landed in 1.2.

The "wrapping the optionals in a tuple and using switch to pattern match" hack always seemed dirty, and this is a huge step in the right direction for code readability.

← PreviousPage 3 of 3