IBM has close to no momentum behind their cloud offerings compared to the big three.
I don't see how IBM will push for Swift in the future. They already pulled out (?) of the swift server working group, and didn't have the kind of pull to begin with.
IMO the most important reasons for the slow adaptation is lacking cross platform functionality (currently no upstream windows support + poor linux tooling) and questionable API design. Both make it difficult for new developers to give swift a try. Luckily, windows supportis supposed to come with the next version in a few months.
The API design is probably very subjective, but comparing the example in the blog post I don't understand how anyone could prefer:
To play the devil’s advocate, I think time.time() is more vague than intuitive. What value does it have? 0? Current time? In what time zone? Is it monotonous?
I don't see how IBM will push for Swift in the future. They already pulled out (?) of the swift server working group, and didn't have the kind of pull to begin with.
IMO the most important reasons for the slow adaptation is lacking cross platform functionality (currently no upstream windows support + poor linux tooling) and questionable API design. Both make it difficult for new developers to give swift a try. Luckily, windows supportis supposed to come with the next version in a few months.
The API design is probably very subjective, but comparing the example in the blog post I don't understand how anyone could prefer:
import Foundation CFAbsoluteTimeGetCurrent()
over:
import time time.time()
The python way is much more intuitive IMO.