If you process them does .mjs impede you more thank package.json or pragma (which is oof in JS)?
The cost is small per incident but widespread. And we're imposing it. Why?
-
-
Because there is a path here that doesnt impose problems for .js (people could userland "use module" or parse guess) and
-
The solution doesnt leave tech debt like package json. Doesnt have scaling problems if 3rd mode appears. Is web compatible. And
-
Is clear about what a file is if it is standalone ( like in a gist ). Doesnt cause future forward problems like guessing. And
-
Doesnt go against reluctance of a new pragma when strict one wasnt universal. Is easy to detect and follows what file extensions do. And
-
Doesnt have envs where it prevents support, or doesnt male sense.
-
What does this mean?
-
Works in way that web, node, random CLI tools, OS, etc. can have same mechanism
- 17 more replies
New conversation -
-
-
To avoid higher cost elsewhere?
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.