Given that this alleges to be a beta version and according to its own EULA:
THIS IS PRE-RELEASE, TIME-LIMITED SOFTWARE MEANT FOR EVALUATION AND DEVELOPMENT PURPOSES ONLY. THIS SOFTWARE SHOULD NOT BE USED IN A COMMERCIAL OPERATING ENVIRONMENT OR WITH IMPORTANT DATA.
why do Apple insist on removing any existing Safari 3 install when installing?
If we are supposed to evaluate and develop, then surely it would be prudent to allow a stable version to also be installed alongside for mission-critical usage.
Surely it's a TERRIBLE idea for non-stable, evaluation software to disallow the use of an alternative stable version?
Another point worth making is that if you are purely interested in learning JS, as opposed to simply getting a job done, there's a lot to be said for taking the functionality you use most often from 3rd party libraries (and in some cases, the missing functionality you wish was in your favourite library) and attempting to write your own.
I was forced into doing this a year or so ago by a client who refused to use any code that we couldn't fully support, and didn't own the IP of (they're a major financial institution, so there was some logic behind this stance, but they never grasped why it didn't need to apply to JS).
As a result I've now got a stable library which is 1/4-1/3 the size of jQuery or Prototype and will allow me to accomplish 99% of what I do on a day-to-day basis quickly, easily, and is stable x-browser.
I appreciate this isn't for everyone, and it's taken a year of near continual work to get to this stage, and there's still a lot of ongoing work.
Before anyone asks, the original version of my home-rolled library is not mine to distirbute, but I am taking some of the things I've learned and working on my own version as and when I find time/motivation which I may well release into the wild if it ever gets mature enough - http://in.tellig.net/2008/11/21/elmojs-and-etherpad/.
All the simple programs have been written.