The new Intl API while amazing, sounds like a big lost opportunity for built-in modules. I feel sorry seeing this new API in the global scope of node 12 (and the web)
-
-
because URL was already there, we can’t do nothing about it... but now looks like there is a better approach, I just would like new apis to follow this new “modern” way
-
I see. I'm happy for us to move more API development out to built-in modules once they're proven out for more things. That said, there doesn't seem to be a coherent policy for why Node can't/won't add globals and it continues to confuse me.
- 1 more reply
New conversation -
-
-
I guess my point is that, i would like to see less: globalThis.NewThing and more of import 'std:new-thing'
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Adding more globals is it harder on tooling, specifically unit testing and resolving different modules for various builds. I'd much rather import requestAnimationFrame than having to patch it on globals to make it work in various environments, or be able to unit test callbacks.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
(dependent: importer, specifier: string) can be paired per source text doing the importing, so unique / constrained forms per import. globals views are not capable of such currently. introducing a powerful API as a shared global doesn't work great on multi-tenant envs.
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.