2 ms·
This article has a point. But, as in all things software, "it depends." It depends on what the tools are, and what we are writing. In my own case, I have the
by ChrisMarshallNY 7y ago
This article has a point.
But, as in all things software, "it depends."
It depends on what the tools are, and what we are writing.
In my own case, I have the luxury of writing fully native Swift code for Apple devices. I don't need to work with anything off the device, except for fairly direct interfaces, like USB, TCP/IP or Bluetooth.
Usually.
I have written "full stack" systems that included self-authored SDKs in Swift, and self-authored servers in PHP/JS.
I avoid dependencies like the plague. Some of them are excellent, and well worth the effort, but I have encountered very few that really make my life as an Apple device programmer that much easier. The rare ones I do use (like SOAPEngine, or ffmpeg, for instance), are local to the development environment, and usually quite well-written and supported.
If I were writing an app that reflected server-provided utility on a local device, then there's a really good chance that I'd use an SDK/dependency with network connectivity, like GraphQL, or MapBox. These are great services, but ones that I don't use (at the moment).
I'm skeptical of a lot of "Big Social Media" SDKs. I believe that we just had an issue with the FB SDK.
That said, if I were writing an app that leveraged FB services, I don't see how I could avoid their SDK.
So I write fully native software with Swift, and avoid dependencies. That seems to make my life easier.
But Xcode is still a really crashy toolbox.