3 ms·
Yes, but program correctness and the ability to scale should easily offset worrying about 10MB. Look at all the work so me like John Carmack puts into correctn
by melling 11y ago
Yes, but program correctness and the ability to scale should easily offset worrying about 10MB.
Look at all the work so me like John Carmack puts into correctness, for instance.
http://www.gamasutra.com/view/news/128836/InDepth_Static_Code_Analysis.php http://www.gamasutra.com/view/news/128836/InDepth_Static_Cod...
"NULL pointers are the biggest problem in C/C++, at least in our code"
- simonh 11y agoMobile over the air download limits. Nowadays with the limit at 100mb it's not as bad as it used to be when it was 50mb, or even 20mb back in the day. Still, you really don't want to go over that threshold if you can possibly avoid it
- melling 11y agoApple increased the limit 2 years ago. It's not even worth mentioning. http://www.macrumors.com/2013/09/18/apple-increases-over-the-air-app-store-download-limit-to-100mb http://www.macrumors.com/2013/09/18/apple-increases-over-the... You paid a small Swift binary size penalty for a year in exchange for safer code that you'll support for the next several years.
- BillinghamJ 11y agoI'm not convinced about this at all. Adding 10MB to the size of an app is actually a really big deal, especially in countries where 4G has not reached the majority of people yet. It is not hard to deal with null pointers, and the way Obj-C handles them is particularly friendly (returning nil on any message to a nil pointer).
- Cthulhu_ 11y agoIf your target audience is countries with those limitations (and no wifi) and the 10 MB overhead is too much, you'd probably opt to stick with objective-C for a while longer, then.
- darkFunction 11y agoI absolutely agree with you. But as a startup moving at full speed and burning through investment, it's not just the size you need to take into account. It's the maturity of the tools, especially around unit testing (and automated testing), the stability of the IDE, and a whole host of issues where you don't have the luxury of wrestling with workarounds for an immature environment. You speak of program correctness but we have a whole suite of tests, analysis and coverage that would have to be migrated to work with Swift and obj-c and it's an investment we can't take lightly. Having said that, I think it is about time to move to Swift and it's going to be in the spotlight for us soon.