Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Proposal: Rename engines #39
I'm proposing that we change the name of the category of things that convert JSON to Ruby objects and Ruby objects to JSON. Right now we call them "engines". I think that name is suboptimal name for a few reasons:
I'd offer the following alternatives to "engines", none of which are perfect, but any of which I believe would be an improvement:
We could also just call them "libraries", but I think that's even more generic (and therefore worse) than "engines".
Or we could stick with "engines".
This is a hardcore breaking change
This comment has been minimized.
This comment has been minimized.Show comment Hide comment
I mean, I suppose we could allow users to specify different libraries to parse and serialize but that would add a ton of complexity for a use can that I'm not sure actually exists.
In a theoretical universe where the JSON library with the best parsing performance had lousy serialization performance and the library with the best serialization performance had lousy parsing performance, someone might want to use different libraries, but we do not live in such a universe.
Despite the name, MultiJSON wasn't really designed for using multiple JSON libraries. It was designed for allowing you to use the best one. Maybe we should change the name of the whole enterprise to BestJSON.