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
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}
-
-
-
We could've tossed out all (!) of the built-ins, creating a much smaller API. Stdlib through imports is vastly superior
- 4 more replies
New conversation -
-
-
yup, we've got a stdlib now and yeah it's there so we should use it. But if we had none we'd be better off and I'd be using ramda
-
does this make sense? Trying to put down the "what if" vs "ugh, reality"
End of conversation
New conversation -
-
-
it's syntactic sugar that's actually useful: less stuff to name, makes tiny pkgs work better together e.g.https://twitter.com/yoshuawuyts/status/768859194913132544 …
-
I would go ahead and ditch all built-ins tho; every built in that's part of JS up until this point would be pretty much moot hmm
End of conversation
New conversation -
-
-
lua might be a good example. Half the internet runs on it. It has no stdlib. People complain but nobody cares b/c it's fast af
-
like: if there's no stdblib we'll get great solutions like ramda to fill up the gap. With heaps convenient syntax. I wouldn't mind
- 1 more reply
New conversation -
-
-
yes, google will keep making v8 fast and JS will still run everywhere regardless of what spec makers do. But as a language? nah
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
yeah that's true, but then we're stuck in ESFantasy land - which is cool with corporate backing but not just by myself
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.