5 ms·

If you had followed what Owens has written and done in Swift, you know that he has worked and pondered the language quite a bit. Dismissing it as due to "blub"

by lerno 12y ago

If you had followed what Owens has written and done in Swift, you know that he has worked and pondered the language quite a bit. Dismissing it as due to "blub" is disingenuous. Aside from brushing away the value of his opinions, such a statement also implies that Swift is in some way sufficiently removed from mainstream languages as to feel "foreign". That is not true. Swift is a pragmatic amalgam of features from many modern languages. The issue here is that many of the ideas are not fully realized and stunted to work within the constraints for the language (such as seamless C/ObjC interop). This is what is causing generics to only be halfway there (and same with several other features). In generics, Swift aims for strictly typed, reified generics, but then leaves you only with very crude tools to create them with. Generics in Swift is an exercise in frustration. Owens' feelings for generics might have changed if the support had been more complete.

dkarapetyan 12y ago
When it comes to programming language reviews I don't think there is any value in them regardless of who is doing the review. Steve Yegge in one of his epic posts explains why everyone should design a language from scratch to see what the process is like. Once you do that the magic and wonder disappears and you realize both how hard and easy it can be depending on what constraints you have. Here's a nice starting point http://nathansuniversity.com/ http://nathansuniversity.com/.
- lerno 12y ago
  You're the one who evoked "blub", essentially insinuating that the reason for his inability to appreciate the language was due to him not being used to it. I addressed that, and your counter with that it's "hard to make a programming language"? Of course it's hard. And the problem with Swift is that it tried to do so many things at once, even with the hard constraints it had. And this is precisely why the language ends up short of its goal. Speaking of ObjC 3.0, the point of the author is simply that an incremental improvement on ObjC which simply removes redundant syntax from ObjC would have been just as useful but much easier to get up and running. The features that Swift tries to incorporate are admirable and interesting for the most part, but the implementation falls short because it's quite simply too ambitious to even reach "usable" until 3.0 or something.
  - dkarapetyan 12y ago
    You're putting words in my mouth. I did not say "it is hard to make programming languages". It is a skill like any other that can be improved with sustained practice. My point is most of these conversations about the merits/demerits of languages are less than useless. Here's a programming language checklist http://colinm.org/language_checklist.html http://colinm.org/language_checklist.html and another one about the history of programming languages http://james-iry.blogspot.com/2009/05/brief-incomplete-and-mostly-wrong.html http://james-iry.blogspot.com/2009/05/brief-incomplete-and-m.... This post was just a variation of the checklist which indicates to me the author is not really interested in any kind of deep analysis of the language and is just publicly bitching and moaning. That to me is an indicator of the blub disease.
    - lerno 12y ago
      Regarding "blub" I already told you that this is unlikely given the amount of dialog and work Owens has done in the language so far. He is one of the few people who has written in depth about the language (not tutorials) If you didn't like my attempt to make sense of your non-sequitor about programming languages, you should perhaps reconsider your approach to commenting / writing. In any case, his post is to be understood as a "current feelings about Swift" after writing code and blog articles about different features in Swift, starting with this one http://owensd.io/2014/06/09/swift-future-for-app-developers.html http://owensd.io/2014/06/09/swift-future-for-app-developers.... Just saying that he is pulling opinions out of the blue ("not really interested in any kind of deep analysis") is blatantly false, as his other articles IN THAT BLOG amply demonstrates.
    - coldtea 12y ago
      >Regarding "blub" I already told you that this is unlikely given the amount of dialog and work Owens has done in the language so far. He is one of the few people who has written in depth about the language (not tutorials) Well, if said post is anything to go by, that's not saying much...
      - lerno 12y ago

by lerno 12y ago

dkarapetyan 12y ago

When it comes to programming language reviews I don't think there is any value in them regardless of who is doing the review. Steve Yegge in one of his epic posts explains why everyone should design a language from scratch to see what the process is like. Once you do that the magic and wonder disappears and you realize both how hard and easy it can be depending on what constraints you have. Here's a nice starting point http://nathansuniversity.com/ http://nathansuniversity.com/.

lerno 12y ago
You're the one who evoked "blub", essentially insinuating that the reason for his inability to appreciate the language was due to him not being used to it. I addressed that, and your counter with that it's "hard to make a programming language"? Of course it's hard. And the problem with Swift is that it tried to do so many things at once, even with the hard constraints it had. And this is precisely why the language ends up short of its goal. Speaking of ObjC 3.0, the point of the author is simply that an incremental improvement on ObjC which simply removes redundant syntax from ObjC would have been just as useful but much easier to get up and running. The features that Swift tries to incorporate are admirable and interesting for the most part, but the implementation falls short because it's quite simply too ambitious to even reach "usable" until 3.0 or something.
- dkarapetyan 12y ago
  You're putting words in my mouth. I did not say "it is hard to make programming languages". It is a skill like any other that can be improved with sustained practice. My point is most of these conversations about the merits/demerits of languages are less than useless. Here's a programming language checklist http://colinm.org/language_checklist.html http://colinm.org/language_checklist.html and another one about the history of programming languages http://james-iry.blogspot.com/2009/05/brief-incomplete-and-mostly-wrong.html http://james-iry.blogspot.com/2009/05/brief-incomplete-and-m.... This post was just a variation of the checklist which indicates to me the author is not really interested in any kind of deep analysis of the language and is just publicly bitching and moaning. That to me is an indicator of the blub disease.
  - lerno 12y ago
    Regarding "blub" I already told you that this is unlikely given the amount of dialog and work Owens has done in the language so far. He is one of the few people who has written in depth about the language (not tutorials) If you didn't like my attempt to make sense of your non-sequitor about programming languages, you should perhaps reconsider your approach to commenting / writing. In any case, his post is to be understood as a "current feelings about Swift" after writing code and blog articles about different features in Swift, starting with this one http://owensd.io/2014/06/09/swift-future-for-app-developers.html http://owensd.io/2014/06/09/swift-future-for-app-developers.... Just saying that he is pulling opinions out of the blue ("not really interested in any kind of deep analysis") is blatantly false, as his other articles IN THAT BLOG amply demonstrates.
  - coldtea 12y ago
    >Regarding "blub" I already told you that this is unlikely given the amount of dialog and work Owens has done in the language so far. He is one of the few people who has written in depth about the language (not tutorials) Well, if said post is anything to go by, that's not saying much...
    - lerno 12y ago