jakobkummerow

My key point is that I'd be in favor of something that doesn't have to be built into every engine/browser because it is built from existing primitives and can be...

> is your proposal that TC39 not standardize additions to the JavaScript and built-in libraries, and move instead towards coordinating the authoring and endorsement external libraries instead, which would be...

I think it would be particularly great if the design of the standard library were such that both options are viable. I.e., if there is a separately distributed/hosted version that...

So you're saying it's easy to spec a standard library that way -- great! Let's have one!

We clearly do not have the kind of standard library that I have described above as being one I would like to have. Maybe we never will; Dan asked what...

Fine -- I didn't mean to get hung up on such details; as I said: > I don't know if any of these will turn out to makes sense The...

> A standard that may or may not be present is one you can’t rely on without providing a fallback (and having a mechanism to do so). Of course, and...

> Just to make sure I understand, is the main difference between your proposal and #31 (comment) specifically about where the BigDecimal constructor lives--in a property of the global object...

> global object vs module exports That's an implementation detail I don't really care about. Both are polyfillable IIUC. > is one way to think of your idea as #35...

(Not to get involved into the discussion here, just to clarify my point: I think it's uncontentious that `a + b` is cleaner than `a.plus(b)`; I'm certainly not denying that,...