Also curious why would one be proud of having an LLM rewrite something that there is already a library for. I personally feel that proud LLM users boasting sounds as if they are on amphetamines.
Also curious why would one be proud of having an LLM rewrite something that there is already a library for. I personally feel that proud LLM users boasting sounds as if they are on amphetamines.
It made a webmail client. Not a jmap library.
Not sure I understand, wouldn’t a webmail client in rust need client code like this or to use a library like this?
Yeah but it’s like saying, “why are you impressed with Claude making a car when there are plans for an engine online?”. Even if Claude used that code (it didn't), it made the whole car. Not just an engine. There’s a lot more stuff going on than simply calling a backend mail server over jmap.
And fyi, jmap is just a protocol for doing email over json & http. It’s not that hard to roll your own. Especially in a web browser.
Your initial claim talked about jmap and this looks to me like a full implementation of the RFC in rust. That is the hard part of an email client IMO so I’m not sure I’d agree with your analogy, but you’re saying it made a web app which called a library like this?
Would be interesting to see it, did you publish it yet?
> looks to me like a full implementation of the RFC in rust
Only the client parts. And only the client parts its actually using. JMAP is designed to make clients much simpler than servers. A JMAP server needs to actually parse message envelopes - which is way more difficult to do correctly than people think. A JMAP client can just ask the server for pre-parsed messages.
The code is here:
https://github.com/josephg/claude-mail
Claude put its JMAP API wrapper in a child crate (confusingly also called jmap-client).