Comment 9 for bug 1521607
Revision history for this message
| Jamie Hannaford (jamie-hannaford) wrote | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Well, if I'm being completely honest, it was not compatible. I don't understand why a project would want to implement a subset because a cognitive burden is placed on end-users to not only understand JSON PATCH (which is very complicated to begin with), but also on the delta between what's in the spec and what Glance pick and mixes for its codebase.
Because things don't work as expected, and because of this cognitive burden, I didn't extract any value out of the implementation (it certainly wasn't useful for me). I think that if projects want to use JSON PATCH, that's fine, but they must implement it wholly. Otherwise you're introducing a great deal of uncertainty and complexity into something just for implementation reasons, which is irrelevant to end-users.