The docs indicate there are already 2 other go implementations. Why not just use one of those? https://docs.jsonata.org/overview.html

▲

aniceperson 9 hours ago | parent | next [-]

Because 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 5 hours ago | parent | prev | next [-]

Because otherwise they wouldn't have written this meaningless article and contributed to the AI hype.

	▲	zer00eyz 4 hours ago \| parent [-]
		And to market their AI security product.

▲

leonidasv 4 hours ago | parent | prev | next [-]

Those 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.

▲

vova_hn2 4 hours ago | parent | prev | next [-]

Last commits in those repos are 5 and 7 years ago.

	▲	heavyset_go 4 hours ago \| parent [-]
		If 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.

▲

hrmtst93837 3 hours ago | parent | prev [-]

Rewrites happen because nobody wants to debug someone else's half-finished mess, and "just use X" often means inheriting its quirks and gaps.

	▲	grey-area 35 minutes ago \| parent [-]
		Now they have 13k lines of someone else’s mess (the AIs) to manage instead.