Down by the Lake

Introducing GPUImage 2, redesigned in Swift

in
April 16, 2016
GPUImageLogo-Small.png

Back in 2010, I gave a talk about the use of OpenGL shaders to accelerate image and video processing on mobile devices. The response from that talk was strong enough that two years later I started work on the open source framework GPUImage with the goal of making this kind of processing more accessible to developers. In an attempt to broaden the reach of this framework, today I'm introducing the completely-rewritten-in-Swift GPUImage 2 with support for Mac, iOS, and now Linux. This isn't just a port, it's a complete rewrite of the framework.

Read on for how GPUImage 2 differs from the previous iteration, and why I rebuilt it from scratch.

What we learned from rewriting our robotic control software in Swift

in
November 3, 2015
Apple_Swift_Logo.png

At the beginning of this year we started a complete rewrite of our robotics software from Objective-C to Swift, for reasons described here. That rewrite was concluded two months ago, passed testing a month ago, and has been deployed to all of our customers. As a result, I wanted to do a final analysis of the rewrite and what we learned from it.

Read on for the results from this rewrite in Swift.

Swift 2 error handling in practice

in
June 12, 2015
Apple_Swift_Logo.png

This week, Apple enhanced Swift with several additions or changes, bumping it to version 2. Perhaps the biggest change was the introduction of an official error-handling model based on try/catch semantics. At first, I was skeptical about this approach when compared to other techniques (primarily the use of a Result return value), but after applying it to real-world code, I've found it to work extremely well.

Read on for more detail about the new Swift error handling model.

Why we're rewriting our robotics software in Swift

in
December 2, 2014
Apple_Swift_Logo.png

At SonoPlot, we just undertook a full rewrite of our robotic control software from Objective-C to Swift. While at first it might appear crazy to rework a large, stable project in a brand-new language, we did so after carefully examining sources of bugs in our Objective-C application and determining that Swift would prevent a large percentage of them. While we've only just started, we've learned enough so far that I thought there would be value in sharing this.

Read on for more about what led us to rewrite this application, and what we observed when doing so.

Syndicate content