Live data from Hacker News

Show HN: Sosumi.ai – Convert Apple Developer docs to AI-readable Markdown

sosumi.ai

51–60 of 74 posts

Re: Show HN: Sosumi.ai – Convert Apple Developer docs to AI-readable Markdown

#55
post #47

Hm, I would have extracted the markdown from the Swift source code. That’s what Apple uses to generate their pages, using https://www.swift.org/documentation/docc/ . For example, AFAIK, https://github.com/swiftlang/swift/blob/main/stdlib/public/c... is used to generate https://developer.apple.com/documentation/swift/array .

This is only possible for some of Apple‘s open source Swift code, including the Swift standard library. This is not the case for hundreds of other SDK frameworks, such as SwiftUI.

Even for those open source projects, there is still some value added in the generated documentation that isn’t directly available from documentation comments, such as type members and protocol conformances (though a LLM could certainly suss that out with the right context).

Re: Show HN: Sosumi.ai – Convert Apple Developer docs to AI-readable Markdown

#56

"AI-readable Markdown" — can't we just say "Markdown"? I'm serious about this, why are we focussing on making things accessible to AI when they should just be machine-readable and accessible to human beings in the first place? No need to taint this by bringing AI into it.

> why are we focussing on making things accessible to AI Because that’s the authors actual goal? To take a web page that looks fine to human eyes but is unintuitively not accessible to AI. That’s genuinely useful and valuable. Sure it’s no different than converting it to markdown for human eyes. But it’s important to be clear about not just WHAT but also WHY. C’mon now. This isn’t controversial or even bad.

I mean.... it could have broader appeal without artificially restricting its audience

Re: Show HN: Sosumi.ai – Convert Apple Developer docs to AI-readable Markdown

#59

Earlier quoted context omitted.

> why are we focussing on making things accessible to AI Because that’s the authors actual goal? To take a web page that looks fine to human eyes but is unintuitively not accessible to AI. That’s genuinely useful and valuable. Sure it’s no different than converting it to markdown for human eyes. But it’s important to be clear about not just WHAT but also WHY. C’mon now. This isn’t controversial or even bad.

I mean.... it could have broader appeal without artificially restricting its audience

Not everything is for everyone. Y'all are criticising this project's bean soup because you don't like beans.

Re: Show HN: Sosumi.ai – Convert Apple Developer docs to AI-readable Markdown

#60

Earlier quoted context omitted.

> why are we focussing on making things accessible to AI Because that’s the authors actual goal? To take a web page that looks fine to human eyes but is unintuitively not accessible to AI. That’s genuinely useful and valuable. Sure it’s no different than converting it to markdown for human eyes. But it’s important to be clear about not just WHAT but also WHY. C’mon now. This isn’t controversial or even bad.

I mean.... it could have broader appeal without artificially restricting its audience

If you think it has less appeal because it was built for and advertised for AI that’s a you problem.
Post reply on HN