If ES3 had had an addition of a `::` operator as a shorthand for an efficient `.bind()` we could've probably tossed out most of ES{5,6,7}
-
-
Replying to @yoshuawuyts
e.g. it's inconvenient to write `reduce(map(filter(arr), op), op), op)` where `arr::filter(op)::map(op)::reduce(op)` is much more convenient
1 reply 0 retweets 4 likes -
Replying to @yoshuawuyts
We could've tossed out all (!) of the built-ins, creating a much smaller API. Stdlib through imports is vastly superior
1 reply 0 retweets 2 likes -
Replying to @yoshuawuyts
But instead where we're now is that spec makers wield the power to prevent anything they don't like from being a first class citizen
1 reply 0 retweets 1 like -
Replying to @yoshuawuyts
Extending built-ins is an anti-pattern. Convenient syntax to non-destructively extend is unavailable. This is probably the biggest issue rn
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
We're on a track where each new version of JS brings new stuff. Remember left-pad? So spec makers now turned a joke into a spec. Nope
1 reply 0 retweets 1 like
I want a scripting language to be fast, extensible, embeddable and understandable. JS will never become that. There is no bright future
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.