3 ms·

Also a joke: ruby, python, javascript, any other language without a vendor provided IDE. Seriously though, I was expecting a critique of actual Swift, not just

Also a joke: ruby, python, javascript, any other language without a vendor provided IDE. Seriously though, I was expecting a critique of actual Swift, not just someone annoyed that their favourite feature of Xcode doesn't work with Swift. How many versions of Xcode didn't have this feature? I can't find a citation, but I seem to recall it was added around Xcode 4... all other versions of Objective C were jokes, then? I personally find Swift to be incredibly expressive, even though I'm still very new at it. I also find Xcode to be an amazingly powerful and somewhat error prone suite of tools... even with ObjC, though definitely more so with Swift

deleted 11y ago
[deleted]
- kennywinker 11y ago
  Swift has a REPL... have you used it a bunch and found it lacking? (serious question, as I have not used the REPL a lot)
  - deleted 11y ago
    [deleted]
    - honest_joe 11y ago
      RubyMotion
jharger 11y ago
On top of that, his complaints about error messages are... well... not sure the word I'm looking for. I don't even know swift and those error messages don't look that bad to me. The only thing that seemed slightly odd is the Int(...) < Int(...) one... but again I don't know swift, so maybe that's just a badly formed expression (like attempting to compare object references or something).
- deleted 11y ago
  [deleted]
- kennywinker 11y ago
  the clang errors Xcode gives you when using ObjC are generally quite helpful. They should be, as they represent decades of development effort (on GCC and then clang). Swift is notably less verbose, but mostly it's just as an ObjC dev you've developed years of experience and you know what that EXC_BAD_ACCESS probably means you forgot to do... with Swift you're a beginner again.
kylnew 11y ago
I don't think the primary complaint was about not being able to refactor, that's just how he opened. Most of the article is about just how ambiguous and deceiving the errors can be, and all rooting from a similar mistake too.

deleted 11y ago

[deleted]

kennywinker 11y ago
Swift has a REPL... have you used it a bunch and found it lacking? (serious question, as I have not used the REPL a lot)
- deleted 11y ago
  [deleted]
  - honest_joe 11y ago
    RubyMotion

jharger 11y ago

On top of that, his complaints about error messages are... well... not sure the word I'm looking for. I don't even know swift and those error messages don't look that bad to me. The only thing that seemed slightly odd is the Int(...) < Int(...) one... but again I don't know swift, so maybe that's just a badly formed expression (like attempting to compare object references or something).

deleted 11y ago
[deleted]
kennywinker 11y ago
the clang errors Xcode gives you when using ObjC are generally quite helpful. They should be, as they represent decades of development effort (on GCC and then clang). Swift is notably less verbose, but mostly it's just as an ObjC dev you've developed years of experience and you know what that EXC_BAD_ACCESS probably means you forgot to do... with Swift you're a beginner again.

kylnew 11y ago

I don't think the primary complaint was about not being able to refactor, that's just how he opened. Most of the article is about just how ambiguous and deceiving the errors can be, and all rooting from a similar mistake too.