Don’t bother with Swift for iOS development
1bytebeta.com
1bytebeta.com
Did you forget the period in time where Steve Jobs was making that argument and even he got BTFO?
I think that's what he's getting at. That writing your whole solution in Swift or Obj-C doesn't make sense, because then you need to write a whole new solution in Java for Android. Why not have the common components in Javascript, with the specifics in the platform specific lanaguage?
After this statement you've lost me. This is like saying: "Don't we have enough new models of car already? Why develop new ones? My car gets 25 miles per gallon!" As if new problems never crop-up or new, better approaches never develop.
Portable frameworks might have a place where you target extremely simple like forms based stuff. But even then I would personally never deliver something like that to customers. I guess we all have different standards when it comes to quality.
"A revamp of the language is already in the works". Of Javascript? Haha, that is hilarious. Progress on ECMAScript has been a such boondogle in regards to politics, glacial adoption rate of new features and other general fuck ups that we will unlikely see something even close to a modern language in our lifetimes. But, you know Linux on the desktop will take over the world anytime now, won't it?
This is quite condescending. I think there are merits to both choices: going deeper with a native language exploiting all the intricacies of a platform or going wider with an universal language such as JS. What you ultimately choose as technology may depend on various factors there is no clear cut.
first, people build transpiler so that they can build and maintain large codebase without losing sanity.
Then you have react that come with this great idea, immutability, so that they can have saner codebase.
Much of what happen is due to the language deficiency. Which is why some would have gone and consider language like Go.
Why on earth would you want to use Swift when it's harder and more time consuming to implement, takes longer to learn, has worse library support, is harder to hire for, and only targets one platform? Apple really dropped the ball with Swift.
I suppose that "performance mandates it" is a valid reason for wanting to use Swift. But I think for 95% of apps Swift is the wrong technology choice.
Yes, React Native is a path to cross platform, but high quality cross platform apps need OS-specific interfaces anyways. So what do you save?
It's a hard to solve problem. Facebook was once doing a webapp for mobile and it had an average of 1 star in the app store. Now hopefully they learned their lesson and reiterating on an approach. Still it doesn't mean they'll get it.
There's also game development with Metal, how are you supposed to use javascript for high quality rendering.
Swift will be needed and at the very least as a host for your javascript app. And swift is a no brainer improvement over objective c. It's safer and modern.
I agree, there are many other frameworks I should have mentioned. As for high quality rendering with Javascript --> WebGL?
Completely disagree! We can never have enough languages! I'm excited about the new languages to come, that will re-use the best ideas of the existing languages and come up with new, helpful things.
Kind of disappointed with the article. Just because one language (in this case JavaScript) is occupying the space and is "better" than another, doesn't mean that the other language is irrelevant.
But then again I neither program with Swift or ObjectiveC. Or targeting iOS at al so I might be completely wrong...
You can't judge programming languages/efficiency/maintainability by observing from the fence. I just completed the first Swift project. It's fun and easy to work with. Not leaving Swift for JS (or Obj-C), anytime soon.
And now you have two problems....