3 ms·
But IMO Swift started white-collar, too, with its reference-counting, abort-on-integer-overflow, copy-on-write collections, characters whose size in bytes isn’t
by Someone 3y ago
But IMO Swift started white-collar, too, with its reference-counting, abort-on-integer-overflow, copy-on-write collections, characters whose size in bytes isn’t fixed, no (or limited, being GCD-only? I don’t remember exactly) multithreading, etc.
Yes, it was presented as being a systems language, too, but that convinced very few (and still doesn’t convince many, I think. The language is moving there, but it will be a while before it gets there, if ever)
So, why claim Swift more than repeated “Objective-C's mistake of using the component language as the base”?
- mpweiher 3y agoWell, the analogy is incorrect, so yes, it doesn't fit. ¯\_(ツ)_/¯