Take a look at the polyfills for both (linked from the proposal repo readme) - it's not two lines of code, it's not easy to do correctly, and both values and entries are a significantly common use case - which was part of the onus for getting them in the language in the first place.
Can we please not use es-discuss to just naively and loudly complain about things? It's not productive or friendly. Isiah's initial message is a useful way to think about any proposal, syntax or otherwise, even *before* suggesting it to anyone, and to think about what the context might be if/when it's discussed in committee. On Wed, Jul 19, 2017 at 6:46 AM, Mike Samuel <[email protected]> wrote: > On Wed, Jul 19, 2017 at 9:40 AM, J Decker <[email protected]> wrote: > > > > > > On Tue, Jul 18, 2017 at 11:03 PM, Gil Tayar <[email protected]> wrote: > >> > >> Note that the initial discussion was not about not adding features or > yes > >> adding features. It was about adding niche and convenience feature that > will > >> help only in niche situations. > > > > > > oh, you mean like...( accoding to > > https://medium.com/@flaviohfreitas/es8-the-new-features-of-javascript- > 7506210a1a22 > > ) > > > extra builtins Object.values and Object.entries somehow made it in. > > These are both easy enough to accomplish with two lines of code; and they > > certainly didn't make me go 'oh, that would have been useful at...' > > The first line of the original post is "I've noticed lately that a lot > of heavy syntax proposals ...," so I'm pretty sure they don't mean > that. > Object.values and Object.entries require no new syntax. > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
