You’ve spent the last six months or more working on a major overhaul of your app. You’ve refreshed the UI. Improved the app icon. You’ve even added a bunch of new features and removed the crusty old stuff that no one ever uses. You release it expecting universal praise. Instead, you're met with a barrage of angry tweets and a bunch of 1 star reviews from your once happy users.
We computer “experts” have faith in the deterministic nature of our machines. Web apps destroy that faith.
It’s Microsoft Outlook: You almost certainly know what to expect from it. It does its job well, but brings nothing new to the table. If you need Exchange-based mail for work, or want a desktop alternative to the very good Outlook365 web client, it won’t let you down.
InboxVudu generally does a good job of picking out things people are asking me to do.
Given that, I made the pragmatic decision to start using @objc protocols, classes, and collection types where those things make sense, where Swift fought against my design.
And suddenly the language is a joy to use. It’s like Objective-C but with type inference, no .h files, fewer imports, shorter syntax — and I get the things I was missing.
Cyclists in Paris no longer have to stop at every red traffic light - new rules mean that in certain circumstances they can ignore the signals and keep going. The aim is to make the city's roads much safer.
What time is it, @guardian? pic.twitter.com/s8IcQoXLQ0— Martin Bryant (@MartinSFP) August 12, 2015
Thanks for reading.