4 ms·
This whole situation seems a little ridiculous. If code works and has for years, who cares if it is unmaintained? As long as you don't need to modify it and kno
by Night_Thastus 3y ago
This whole situation seems a little ridiculous. If code works and has for years, who cares if it is unmaintained? As long as you don't need to modify it and know its limitations and capabilities, it's fine.
Code doesn't go bad on its own. I've borrowed or integrated code from decades ago just fine many times.
Personally I'd just ignore any and all complaints about that library and move on.
- zozbot234 3y ago> I've borrowed or integrated code from decades ago Isn't that what the author did by vendoring the library within his own project? It amounts to taking over maintenance for the bits of code you use. Sometimes this is bad (copy-and-paste coding, possibly duplicated effort) but when the third-party component is totally unmaintained it becomes quite excusable.
- nicce 3y agoJust a bigger copy-paste from Stackoverflow than normally.
- remram 3y agoThe answer is of course that it doesn't "work" in a lot of ways. It has accumulated many bugs which will never be patched even though the fixes exist, see https://github.com/chyh1990/yaml-rust/issues https://github.com/chyh1990/yaml-rust/issues and /pulls.