9 ms·
The docs indicate there are already 2 other go implementations. Why not just use one of those? https://docs.jsonata.org/overview.html https://docs.jsonata.or
by cjonas 6mo ago
The docs indicate there are already 2 other go implementations. Why not just use one of those?
https://docs.jsonata.org/overview.html https://docs.jsonata.org/overview.html
- aniceperson 6mo agoBecause his prompt said to implement in go, not to check if an go implementation already exists. They have been running kubernetes clusters to parse json, this is not suprising.
- g947o 6mo agoBecause otherwise they wouldn't have written this meaningless article and contributed to the AI hype.
- zer00eyz 6mo agoAnd to market their AI security product.
- vova_hn2 6mo agoLast commits in those repos are 5 and 7 years ago.
- heavyset_go 6mo agoIf they're vendoring the dependency anyway, that wouldn't matter much if they're not using features that were added since 2021. The last release of jsonata was mid 2025, and there hasn't been new features since the last 2022 release until the latest, so it's likely those other ports are fine.
- leonidasv 6mo agoThose are compatible with the 1.x syntax while the gnata is compatible with the 2.x. Also, the repos haven't seen new commits in a long time.
- hrmtst93837 6mo ago[flagged]
- grey-area 6mo agoNow they have 13k lines of someone else’s mess (the AIs) to manage instead.
- lossoth 6mo agoBut this is a different kind of problem. With legacy systems, at least the complexity was somewhat anticipated early in the design process (even if it was incorrect). With automatically generated code, you get something that "works" but with a much vaguer underlying model, which makes it harder to understand when things start to go wrong. In both cases, the real cost comes later, when you're forced to debug under pressure.