3 ms·
Exactly. But these days, everyone likes to bundle in dependencies. Also, for cross-platform SDKs and libraries, the provider may be forced to "reinvent the whe
by ChrisMarshallNY 5y ago
Exactly. But these days, everyone likes to bundle in dependencies.
Also, for cross-platform SDKs and libraries, the provider may be forced to "reinvent the wheel." That may well be worth it, as developer bandwidth, and time-to-market are important variables.
- numbsafari 5y ago> But these days, everyone likes to bundle in dependencies. If the OS and standard libs provide those dependencies, then I don't need to bundle them. I'm thinking of things like the Go or Python standard libraries, or OTP in Erlang. On iOS you have a rich set of built-in frameworks, etc., etc.
- ChrisMarshallNY 5y ago...and you have a huge number of folks that program for iOS in JavaScript, with dozens of dependencies in each project. This can lead to some rather...overfed...applications, and four- or five-digit bug counts.
- numbsafari 5y agoThat sounds like a problem for those developers and their approach, not with the platform on which they are building.
- ChrisMarshallNY 5y agoYup, but these have become so common, in the industry, that they are now synonymous. For example, I no longer trust people that describe themselves as "iOS developers" to know the first thing about actually developing for the Apple ecosystem. In some cases, they don't even know how to use Xcode.