3 ms·

The main point here is that a lot of documentation is straight up missing. Some of the code samples/sample projects also regularly break. I wonder if Apple has

by tpush 7y ago

The main point here is that a lot of documentation is straight up missing. Some of the code samples/sample projects also regularly break. I wonder if Apple has any automation around that.

DagAgren 7y ago
The only two examples he gives for this "a lot" is a completely new framework that was released about a month ago, and a tool that is, honestly, still in development and not part of normal development workflows for Apple platforms.
- chriskrycho 7y ago
  Two notes: 1. SPM has been out (and officially supported as part of the Swift Project) since Swift 3 came out. You can defend it as being "not part of normal development workflows for Apple platforms" if you like, but it has been officially supported for years. People would rightly call this out in any other language; it's fair to call it out here. 2. My very strongly held opinion, as I noted at the end of the article, is that you can't actually call something "shipped" until you've shipped the docs.
  - DagAgren 7y ago
    It is part of the Swift project, but it is not really part of the Apple development ecosystem. It might at some point be, but it is not now, and it is a small side project. And it is not, in general, used when developing for the ecosystem. And you may feel that way about docs, but it is not reasonable to find one single rushed release, and use that as an argument against the entire ecosystem. That is not a reasonable argument.
    - chriskrycho 7y ago
      This isn't one single rushed release. This is perhaps the worst example at present, but it's not particularly unusual: https://nooverviewavailable.com https://nooverviewavailable.com
      - WAHa_06x36 7y ago
        That looks like a pretty good state to me. Not perfect, but nothing is. Certainly not cause for such an inflammatory article.
- cannam 7y ago
  Official documentation may be more important for a framework that is new, especially if it's one that developers are being required or encouraged to switch to.
  - DagAgren 7y ago
    It is still in beta, and only runs on the newest OS versions. Nobody is required to switch to it, nor especially encouraged.

by tpush 7y ago

The main point here is that a lot of documentation is straight up missing. Some of the code samples/sample projects also regularly break. I wonder if Apple has any automation around that.

DagAgren 7y ago

The only two examples he gives for this "a lot" is a completely new framework that was released about a month ago, and a tool that is, honestly, still in development and not part of normal development workflows for Apple platforms.

chriskrycho 7y ago
Two notes: 1. SPM has been out (and officially supported as part of the Swift Project) since Swift 3 came out. You can defend it as being "not part of normal development workflows for Apple platforms" if you like, but it has been officially supported for years. People would rightly call this out in any other language; it's fair to call it out here. 2. My very strongly held opinion, as I noted at the end of the article, is that you can't actually call something "shipped" until you've shipped the docs.
- DagAgren 7y ago
  It is part of the Swift project, but it is not really part of the Apple development ecosystem. It might at some point be, but it is not now, and it is a small side project. And it is not, in general, used when developing for the ecosystem. And you may feel that way about docs, but it is not reasonable to find one single rushed release, and use that as an argument against the entire ecosystem. That is not a reasonable argument.
  - chriskrycho 7y ago
    This isn't one single rushed release. This is perhaps the worst example at present, but it's not particularly unusual: https://nooverviewavailable.com https://nooverviewavailable.com
    - WAHa_06x36 7y ago
      That looks like a pretty good state to me. Not perfect, but nothing is. Certainly not cause for such an inflammatory article.
cannam 7y ago
Official documentation may be more important for a framework that is new, especially if it's one that developers are being required or encouraged to switch to.
- DagAgren 7y ago
  It is still in beta, and only runs on the newest OS versions. Nobody is required to switch to it, nor especially encouraged.