.@wycats Worrisome that folks think it's anywhere *near* time to talk standards. Competition in userspace is great. Let's see where it goes.
@lbljeffmo Plenty of ppl on TC39 are doing userland type systems. Easy to avoid future hostility without seal of approval @littlecalculist
-
-
@wycats Interestingly, tho, those membs want to ack JS TSyses and others seem to prefer they're never spoken of@littlecalculist -
@lbljeffmo I see types as similar to macros. Have their place, but unclear if needed in the language to be useful.@littlecalculist -
@wycats@lbljeffmo@littlecalculist Like anything in tech, you need some buy-in/agreement to build on top of it. Even if it's not in engines -
@sebmarkbage I can't understand why buy-in from TC39 is required here. Help me.@lbljeffmo@littlecalculist -
@wycats@lbljeffmo@littlecalculist Your code should be portable across browsers. It should also be portable across tools. An ecosystem. -
@sebmarkbage Ecosystems don't need TC39's approval. See node.@lbljeffmo@littlecalculist
End of conversation
New conversation -
-
-
@wycats@lbljeffmo@littlecalculist As I understand it, the champion model is about working without needing a seal of approval for details. -
@sebmarkbage I don't see the point of even bothering with the champion model now. Just Do It.@lbljeffmo@littlecalculist - End of conversation
New conversation -
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.