I mean we are talking right now. Disagreeme t does not mean I will shut you up in any way
It seems we should all be able to come to agreement at least on that assessment if it's purely technical.
-
-
I dont think there is an agreement on what is important both currently and future wise
-
Whats the technical problem with .mjs that exists in future? With .js we have pragmas, grammar collisions, or package.json debt
-
And those problems compound when the use cases start exposing those. Does .mjs in some way?
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.