60 karma · joined February 11, 2013
Even the main Amazon shopping app is less than 100mb.
I feel like what this article is saying is that, just guzzling oil isn't good for you, which is obvious, but in small doses, is it ok?
One big issue I've noticed is that the app is borderline unusable on older devices (iphone 4). This may explain the huge number of people who are reporting these issues, which certainly happen less on newer devices. I've noticed what looks like a small UI hickup on my 5s will crash the iphone 4.
I think at the end of the day, our brains have a limited power to make tough decisions, and it's wise to clearly define a programmers tasks so he/she doesn't have to make them.
https://docs.google.com/document/d/1y9hStonl9wpj-5VM-xWrSTuE...
In theory, Go could absolutely be used for android development
Knowing apple, I feel that they would have an off the shelf solution that you could just push code to. Almost like a parse type solution, integrated through Xcode.
It would make it a no brainer language to use for a mobile app, because you could kill two birds with one stone. To date however, apple has made no comment about cross platform development
I guess my point is try to look for resources your company puts out before trying to create your own
I don't like the comparisons to Go in this article. I'm an iOS developer who has dabbled in Go, and I'd actually argue the opposite.
For me, there is little reason to immediately switch to Swift. I can still use ObjC, and in fact, I'd expect problems when switching to Swift.
Go, however, had many incentives to learn. Easier deployment, speed, concurrency, etc.
As usual, Wired has over simplified the argument