5 ms·
> Some people with common sense must have joined the party More likely the language just matured. I'm glad they were not afraid to iterate as it is hard to get
by AsyncAwait 8y ago
> Some people with common sense must have joined the party
More likely the language just matured. I'm glad they were not afraid to iterate as it is hard to get everything right on the first try and being stuck with a suboptimal design for the next 20 years would have been much worse.
- kylnew 8y agoAgree with this comment. If you’ve watched the community work at this language it’s been a very clear and well documented process. I’ve learned a lot just by watching Swift evolve through proposals.
- pdpi 8y agoIt's funny to bring this comparison up (since Graydon is now on the Swift team), but Rust _also_ iterated like mad and took a while to mature — however, they waited until some degree of maturity before they called it 1.0, and have since been incredibly cautious about breaking changes. And they did this all of this iterating while building Servo in-house at Mozilla on the unstable version. This is, in many ways, the diametric opposite of what this thread is discussing: pushing out nominally "stable" versions to the outside world, breaking things, but not committing internally.
- deleted 8y ago[deleted]
- AsyncAwait 8y agoI agree they probably shouldn't called Swift a 1.0 so soon, but I ascribe that to Apple management not allowing them to come out of the gate with something labelled 0.x
- bunnycorn 8y agoThis. Apple prides itself on "not shipping beta products", which kind of BS.
- innagadadavida 8y agothis only applies to products that normal users interact with - unfortunately it does not apply to anything they do that is targeted to developers.