2 ms·
Since I've worked on International Standardization before I sort of know how the sausage is made, but you always hope for a better sausage. Anyway - browser eq
by bryanrasmussen 8y ago
Since I've worked on International Standardization before I sort of know how the sausage is made, but you always hope for a better sausage.
Anyway - browser equivalence? That, in a lot of things, especially where URLS is concerned, means HTTP equivalence.
A file extension having a specific meaning is not HTTP equivalence or browser equivalence, it is at best Windows OS equivalence where not having mime types understanding meant you had to use the file extensions to identify what 'type' of thing something was.
A hack solution that was maybe necessary (I don't know Windows internals enough to disagree) and that caused me a lot of problems in the years 1999-2009 approximately.
- snek 8y agoBrowsers don't care what extension you serve something as, so it doesn't break the interop we want with browsers if you put your files as `.mjs`.
- bryanrasmussen 8y agomy point exactly, browsers care what mime type you use and the extension is meaningless. I thought I was pretty clear on this matter?
- BillinghamJ 8y agoBoth old "script"-style JS and the new module kind have the same MIME anyway