Realm's developer academy publishes Swift and iOS conference talks and articles on Objective-C, architecture, and mobile development.
HN links it for talks by Andy Matuschak and Wil Shipley, including git as a document format, and for Swift on Android.
You guys may find this talk of interest:
https://academy.realm.io/posts/altconf-josh-michaels-deprecated-incorporated/
Description at the link:
"It’s every Apple developers worst nightmare. Your app is doing well, business is going fine, then all of a sudden BAM! Something changes in Apple’s world and suddenly everything is at risk. Sometimes it’s as simple as Apple deprecating an API you depend on. Other times it’s a policy matter - a change in rules that has Apple requesting that you change or remove your app from the store. Sometimes it is a bug in the platform which you have to hack a creative workaround for. No matter what the specifics, developers should be prepared to handle that day when Apple pulls the rug out. After more than six years of working on apps in Apple’s land I’ve had more than my fair share of these experiences. In this talk I will go through four different examples from multiple developers covering the most common situations in which changes in Apple land can disrupt your app. Through these stories I will offer best practices for handling these difficult situations from how to interact with Apple to how to deal with the gripping frustration that can come along with these challenges. The goal of this talk is to better prepare attendees for that inevitable day when something goes wrong and in doing so help reduce the ambient anxiety many developers feel about the possibility of such problems."
This[1] video with Andy Matuschak helps with refactoring these “Mega” controllers. This[2] article also is good when it comes to breaking down controllers into smaller pieces.
I will admit it’s a hard problem for me. Putting everything into one view controller is so easy and makes certain problems go away. e.g. Storyboards are a lot easier to deal with when their outlets are in the massive view controller. Custom UIviews with storyboards are a huge pain to get working with interface builder.
[1] https://academy.realm.io/posts/andy-matuschak-refactor-mega-controller/
[2] https://www.smashingmagazine.com/2016/05/better-architecture-for-ios-apps-model-view-controller-pattern/
Since Wil Shipleys presentation "Git as a Document Format" (AltConf, 2015, [1]) the idea of using git to track data has stuck with me.
Cool to see another approach at this.
From the first look, I miss the representation of data as plain-old-text-files, but I guess that's a little bit in competition with the goal of getting performance for larger data sets.
Anyway, I am wondering, did somebody here try using plain git like a database to track data in a repository?
[1] https://academy.realm.io/posts/altconf-wil-shipley-git-document-format/
Something just crossed my mind while reading the question, that Swift could be a good candidate. Turns out there are compatibility layers that are based on Swift:
https://www.scade.io
https://academy.realm.io/posts/swift-on-android/
https://blog.readdle.com/why-we-use-swift-for-android-db449feeacaf
I think Delicious Library was for a while at least. I remember the author of it, doing a presentation about using git as storage:
https://academy.realm.io/posts/altconf-wil-shipley-git-document-format/
Can you elaborate? Personally, I thought Swift’s distinction between value and reference types was fantastic. https://academy.realm.io/posts/andy-matuschak-controlling-complexity/