Skip to content

Comment on A new experimental Go API for JSONparent

Comments

"immediately be in need of maintenance" means it needed this update 13 years ago.

encoding/json works perfectly great even today, please troll somewhere else

Please don't use the "troll" accusation to something because you disagree with it. It's weasely.

Obviously encoding/json doesn't "work perfectly", the TFA lists several problems it has, and the need for a new version, and that's directly by the horse's mouth. Is the Go team "trolling" as well?

Second, we're not talking whether it "does the job", which is what you might mean by "works perfectly great".

We're talking about whether it's a good design for the problem domain, or whether it has footguns, bad API choices, performance problems, and other such issues.

It works well enough, despite being clunky, but it has a few issues, including significant performance-related ones.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.