...but I feel that someone would just find an exploit in JS, break out of the sandbox, and use that to run a native demo instead.
While you could do some funky stuff with IE6 JS, you also couldn't really do anything. Don't forget how utterly slow JS was back then, not because the computers were slower, but because it was interpreted and run token-by-token in a very inefficient manner. This, and nobody took it seriously then as a language to write actual applications in. If a scener had to do something splashy in the browser, they'd go for Flash (and still groan about its lack of performance).
If you told someone back then about "asm.js", they'd think you were making a joke, and a pretty funny one at that (like if you told them Microsoft would become a platinum member of the Linux Foundation kind of joke back then).
> ...but I feel that someone would just find an exploit in JS, break out of the sandbox, and use that to run a native demo instead.
Well, there's rules. There always have been rules. You can't read out default icons, themes, desktop background images from the system folder to obtain some nice stock graphics for use in a 4096 byte demo, either.
If your entry hacks the compo machine and doesn't do it with an extreme amount of grace and style, expect to be booed off stage. With sufficient style and awesomeness, you might just get disqualified :)
IE6 seems to me like an arbitrary limit that just makes life horrible without much gain. i don't think sceners are going to target retro browsers soon.
Seriously, remembering the stuff I had to deal with, in today's world of the "modern browsers", I feel like I changed my profession completely. In other words, I'm afraid that me from 10 years ago wouldn't be able to understand so much from the front-end code I write these days and I'm also not sure about the vice versa. The opposite are, although that I don't enjoy the language too much, my Java projects which feel like they are immortal. I wonder if and when JavaScript will be that mature.
The other thing is that Sun owned the standard. So even if you were IBM and were making your own runtime environment, you couldn't call it Java unless Sun agreed. Imagine if you had multiple vendors supplying a JRE and several of them were intentionally breaking their versions to lock users into their implementation.
Lately the browser vendors have started to work a little bit better with each other, but I doubt it will ever be like Java.
You don't have to imagine. Just tried it:
http://i.imgur.com/zBNkKTu.png
Netscape IFC, 1996-1997 vintage. Compiles and runs like a champ on JDK 8, current OS X. Just like it did on JDK 1.
However, in the end, we are still getting something close to Java with Web Assembly (Stable byte-code-like platform and potentially many languages targeting it).