Actually, it wasn't 10 days. As I recall (and I was at Sun at the time in the 'liveoak' group which was to become the Java group) Netscape already had been thinking along these lines and something they called 'netscript' which was their view of how to increase the interactivity of web pages. The original suggestion was to flush it and go with Java to fill this niche, but it was pointed out that having a 'light weight' interpreter already in the browser was useful when all you needed was a "little" interactivity (like a pop up over a form field to tell you what it wanted). No doubt somewhere I've got a 1/4" (QIC) tape with my old Sun email which would let me tell you definitively but that is my recollection. There was concern that people would not know which to use 'netscript' or 'java' and so somebody (and I don't recall who) suggested it be called 'javascript' so that it would be clear it was a lighter weight way of adding interactivity than 'Java'. (most folks at the time thought of 'scripting' languages as light weight languages). The thought being "If its small and trivial just do it in javascript, if its bigger and more sophisticated step up to the power of Java." At the time I don't think anyone anticipated how much could be put into Javascript, nor how tight fisted Sun would become around Java.