Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I found an explanation. Reading between the lines I think he found something less abysmal than YAML.

https://github.com/dtolnay/serde-yaml/releases/tag/0.9.34

> As of this release, I am not planning to publish further versions of serde_yaml as none of my projects have been using YAML for a long time, so I have archived the GitHub repo and marked the crate deprecated in the version number.



Hm... might still have been better to first ask around if anyone is willing to maintain it instead of marking it as deprecated?


From what I can tell this is a second order effect. No advisory was made against serde-yaml, it was made against rust-yaml. The maintainer of serde-yaml I believe just took the opportunity to mark it as deprecated to ensure people don't migrate there.


I'd think of it as a smart move considering how entitled, aggressive and demanding open source software users have become over maintainers.


Yeah, I'm really disappointed reading the comments here. This is his project, he can do whatever he wants with it, including delete and forget about it. The author doesn't owe you anything. Just use a fork or another implementation. This isn't the end of the world.


> The author doesn't owe you anything.

I don't think anyone is claiming he is legally required to do it. Just that it would be nice. But in this case I think he did try to look for someone anyway.


He'd been looking for a serde-yaml maintainer for a while, and none ever popped up.


Not the author, but I assume he is not against you taking over. Code is still there if you are willing. (It is not too late)


I'm not a particularly big fan of YAML either I'm afraid, so I would probably choose some other way-to-learn-rust...




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: