Re:Xcode 14 unintentionally increases app size
by AlfeG on Friday November 11, 2022 @01:05AM
(#33557778)
Should I write my own QR parser or just use available one.
Should I write my own crypto algo or just use battletested one.
Every line I write - line I need to support.
Re:Xcode 14 unintentionally increases app size
by hulitu on Friday November 11, 2022 @01:13AM
(#33557823)
> Should I write my own crypto algo or just use battletested one.
Why would the "battletested" be better ? It is "battletested" by the user, anyway.
> Every line I write - line I need to support.
So you prefer to support someone elses code instead of yours ? ( because it is battletested - just like log4j was)
Re:Xcode 14 unintentionally increases app size
by nomel on Friday November 11, 2022 @01:39AM
(#33557944)
> Why would the "battletested" be better ? It is "battletested" by the user, anyway.
Your tense is incorrect there. "Battletested" means that past users have experienced the carnage of war, so current users can enjoy peace. Your second usage would need to be changed to present tense, like "battletesting", where you subject them to suffering.
Re:Xcode 14 unintentionally increases app size
by piskerpan on Friday November 11, 2022 @02:16AM
(#33558089)
I’m with you on that, but the two are not mutually exclusive. I don’t know how it is exactly in Xcode, but in my field there’s a huge difference between importing a whole kitchen sink named “moment.js” or a few “date-fns” functions.
This is it. Developers on broadband and tight budgets don't care about app size. On the App Store there's usually no direct correlation between app size and conversion rate: the app will eventually be available anyway.