ljharb at gmail.com
Thu Nov 2 04:23:58 UTC 2017
I'm really not sure what "civil war" you're referring to; nor do I agree
Plain objects don't come with JSON representations "baked in" because
functions, undefined, regexes, dates, etc all don't serialize.
Frontend development is not "alienated"; in fact, the additions made in ES6
are widely loved overall (even though there are, as with anything,
On Wed, Nov 1, 2017 at 8:43 PM, kai zhu <kaizhu256 at gmail.com> wrote:
> any thoughts? i'll break the ice with a quora question i recently answered
> quora question:
> answer posted:
> >the primary reason is because traditional oop skills gained from
> because plain-objects come with JSON.stringify/JSON.parse baked-in, while
> classes require needless extra serialization/deserialization routines which
> heavily i/o based). i would say many people burn-out from
> frontend-programming because they can’t cope with debugging all the i/o
> edge-cases serializing/deserializing their custom classes.
> managing the program-state like a baton, constantly passing it
> back-and-forth between the browser’s ui and various backend-servers /
> persistent-storage. plain json-objects utilizing idiot-proof
> JSON.stringify/JSON.parse, are naturally better at this baton-passing
> business than writing classes with custom serializers.
> there's currently a civil war going on in frontend-development,
> between those who don't want to deal with writing extra class-based
> serializers/deserializers and those who do. these 2 different design
> patterns have incompatible styleguides that often break web-projects
> when people try to mix-and-match both together. i don't have a simple
> solution to this issue, but tc39 should be made aware of it as they
> es-discuss mailing list
> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss