An “AI” that makes text “AI”-readable. How does that make any sense?
Show HN: Sosumi.ai – Convert Apple Developer docs to AI-readable Markdown
21–30 of 74 posts
Re: Show HN: Sosumi.ai – Convert Apple Developer docs to AI-readable Markdown
#22I think it's safe to assume most big players have browser rendering enabled (I hope so). imo AI is struggling with a lot of languages that are not as popular as javascript, mostly because it's more niche and you don't get a lot of good examples on the web.
In my experience, coding agents seem to do a normal fetch when provided links. Which makes sense — headless browser automation is expensive, and only really necessary for interacting with a webpage.
But with these RLHF'd AIs, being confident and helpful as they are, it took me a while to realize that they couldn't actually read the Apple developer links I was giving them. Like a kid who can't read the chalkboard, but doesn't realize they need glasses.
Re: Show HN: Sosumi.ai – Convert Apple Developer docs to AI-readable Markdown
#23I don't even bother trying to render docc catalogs into JS. It's a royal pain that breaks easily. If GitHub could support .docc files, that would be great. Otherwise, I still use Jazzy Docs.
Once upon a time, I built a project called `swift-doc`, which eventually got Sherlocked. I think what I was most upset about was their decision to call their thing "DocC". Like, adding redundant consonants to avoid name collisions is my shtick.
Long live Jazzy.
Re: Show HN: Sosumi.ai – Convert Apple Developer docs to AI-readable Markdown
#24I don't even bother trying to render docc catalogs into JS. It's a royal pain that breaks easily. If GitHub could support .docc files, that would be great. Otherwise, I still use Jazzy Docs.
Once upon a time, I built a project called `swift-doc`, which eventually got Sherlocked. I think what I was most upset about was their decision to call their thing "DocC". Like, adding redundant consonants to avoid name collisions is my shtick. Long live Jazzy.
I love your stuff!
Thanks!
Re: Show HN: Sosumi.ai – Convert Apple Developer docs to AI-readable Markdown
#25> "Ever notice Claude struggling to write Swift code? " Yes, that is why I quit using Claude and swapped to ChatGPT about a year ago. I've had substantially less issues with GPT.
ChatGPT does swift and objc remarkably well including UIKit and core data. Its gotten much better for project files with gpt5-mini
Re: Show HN: Sosumi.ai – Convert Apple Developer docs to AI-readable Markdown
#26This is awesome and timely for me...going to give it a whirl. Thanks for building. Also, there should totally be an easter egg where clicking something somewhere plays the sound!
Great idea! I just added that. Try clicking the icon in the header.
Re: Show HN: Sosumi.ai – Convert Apple Developer docs to AI-readable Markdown
#27It is for the same reasons LLM are struggling to produce something that compile in Rust? I was under the impression that most of Rust documentation was plain HTML.
Re: Show HN: Sosumi.ai – Convert Apple Developer docs to AI-readable Markdown
#28Wasn’t one of the benefits of AI that we don’t need special documents for AI to understand the data?
Re: Show HN: Sosumi.ai – Convert Apple Developer docs to AI-readable Markdown
#29How to reliably HTML to MD for any page on the internet?
I remember struggling with this in the past
How hard would it be to build an MCP that's basically a proxy for web search except it always tries to build the markdown version of the web pages instead of passing HTML?
Basically Sosumi.ai but instead of working on only for Apple docs it works for any web page (including every doc on the internet)
Re: Show HN: Sosumi.ai – Convert Apple Developer docs to AI-readable Markdown
#30Could you share what is your motivation behind doing whole domain and web hosting ? Personally I feel that this whole AI induced problem should even exist in the first place, but even then it is ridiculous, that you have to query some web api to solve this problem, why not just publish parsed and converted to .md set of local files and be done with it.
I agree, it'd be great if Apple provided accessible documentation in the first place. Time was, Apple published self-contained docsets that you could download and read offline. Apple's ToS pretty explicitly forbid the kind of automation required to download everything. But even if someone did that, it'd only be a snapshot in time. And a lot can can change between OS releases. As for the hosted web app, I wanted to pr…
Yeah, pre Swift documentation was very sufficient, dense and locally explorable, since then documentation started to resemble .h copy pasta without comments.