4 ms·
I guess the idea is to use URL's for importing packages. And have an extra security layer in the runtime. I've done some concept/prototype for this but in the
by z3t4 8y ago
I guess the idea is to use URL's for importing packages. And have an extra security layer in the runtime.
I've done some concept/prototype for this but in the browser, and the main complaint is that it takes a few extra ms the first time you run the program. But as this is meant for servers and not impatient users, the extra startup time should not be a big issue.
- scottmf 8y agoImporting URLs is how ES modules work afaik
- WorldMaker 8y agoRight, the pluggable Loader spec [1] can keeps getting kicked down the road, and the Browsers haven't agreed yet on Node-style or non-URL-based loading. To the Browsers, URLs "just work" and is how they've always done things, and figuring out Node-like package boundaries or mapping package names to URLs hasn't seemed like a priority to them yet. [1] https://github.com/whatwg/loader https://github.com/whatwg/loader