3 ms·
The `type` attribute is still there, it only fallbacks to javascript if not set. Nothing besides common sense prevents browsers from shipping with type="text/ru
by ricardobeat 14y ago
The `type` attribute is still there, it only fallbacks to javascript if not set. Nothing besides common sense prevents browsers from shipping with type="text/ruby" support as done here. It's just not a very good idea.
- stormbrew 14y agolanguage was a different attribute pretty much only used by IE and its ActiveX language embedding (which was pretty much only ever used for VBScript). What I'm getting at in a somewhat snarky and roundabout way is that VBScript killed multilanguage support in browsers.
- ricardobeat 14y agoWell, I don't think that holds any water. Multi-language support wasn't and still isn't a good idea; having one good toolchain and cross-browser environment is already a huge effort and far from done, supporting multiple languages would just fragment the ecosystem and slow down progress. There is hardly any popular language today you could embed and get better performance than JS anyway, except for Lua, which barely qualifies as 'popular'. Meanwhile there are a hundred cross-compilers/transpilers out there that give you the kind of syntax you want, without requiring a ton of changes in browsers.
- jstclair 14y agoErik Meier & co used it to enable Haskell as a scripting language (in 1998!). See his "Confessions of a used programming language salesman", HaskellScript PDF: [http://research.microsoft.com/en-us/um/people/emeijer/papers/icfp06.pdf http://research.microsoft.com/en-us/um/people/emeijer/papers...]