id	summary	reporter	owner	description	type	status	priority	component	version	resolution	keywords	cc
212	Builtins: Remove JSON	lth		Lars and Jeff propose that we remove JSON support.\r\n\r\nThe reasons are:\r\n  * JSON encoding and decoding are easily and efficiently written in ES4 (with the use of the new `Map` type circularity checking is efficient)\r\n  * There are diverging opinions in the community about how encoding and decoding should be done (toJSONString vs toJSON in the encoder; the type of filtering that can be done in the decoder).  This will probably mean many users will load their own JSON libraries anyway, reducing the benefit of a standard implementation.\r\n  * It appears that instances of user-defined classes won't be serialized by JSON even if they are pure data containers.  However, such instances would be serialized if they were created by ES3-style constructor functions.  This forces users into staying with ES3-style data even when ES4-style data would be more appropriate.\r\n  * The fact that data that can't be encoded are silently ignored or defaulted to incompatible values (as when NaN becomes null), without any control being given to the program, is a weakness in the current design\r\n  * ES4 has facilities in the `isPropertyEnumerable` method to place `DontEnum` methods on objects, so libraries can safely be loaded by user code.	defect	closed	major	Proposals	4	invalid