Slashdot Mirror
Jazilla Milestone 1 Released
mcbridematt writes "Many of the long time Slashdot readers will remember the Jazilla project to rewrite the Mozilla browser in Java. It went into hibernation in 2000 and I took it over last August. I have completely rewrote the browser which now follows a more Mozilla-like architecture. The Result: Jazilla Milestone 1 has been released. Download it from here. No prizes for guessing that it's Alpha software." Read on below for a list of what Jazilla can do, so far.
"Significant (implemented) features include:
- chrome:// support
- JavaScript implemented for the GUI thanks to the Mozilla.org Rhino engine. HTML Scripting coming.
- GUI in part, uses XUL and W3C DOM
- Written in 100% Java
- Open Source
- Uses the NetBrowser renderer, which is actually based on Jazilla-classic work."
Once you expand and extract this puppy, just cd into the folder it made and, assuming Java is properly installed on your machine, you need only run:
Good luck, and enjoy! The browser's still lacking in many obvious areas, but it does work on a lot of sites. Too cool -- props for all the hard wo\ rk. :-)
dont get me wrong i think its an interresting project but why write in Java a software that is already available on a huge variety of platforms (its mainly the advantage of writing java apps).
also Mozilla is lacking a bit of speed im sure you wont help in java.....
Overuse of the Pumping Lemma causes blindness
Hee. I told him it would get him laid, then forgot to mention it was a joke. A year and a half later, it was just too funny not to let him keep running with it. Shh! My bad!
I think Mozilla is slow enough, thank you.
It allows you to close tricked-into Goatse windows before they are finished. Goatsephobia has changed they way people browse. Slow is in.
Table-ized A.I.
Since half the comments so far seem to be "What is the point" I'll offer one justification.
There is still a serious lack of a good modern HTML browser for embeding in java applications. Swing provides an EditorKit which handles HTML3 reasonable well, but most of the other quality offerings are non free.
Major Java IDEs (Eclipse, NetBeans) have projects to implement something like this. Many other Java applications could potentially benefit. It's a good idea.
This means that when you go to the store to buy an application, you don't buy the "Mac version" or the "Microsoft Windows version." You buy the "Java technology version." And as long as you have the Java Virtual Machine--which is free, and available from a large number of vendors--you can buy the program without having to worry whether it's going to run on your particular computer.
Ok it was kinda a joke but I will address it more seriously this time.
1. Java is slow. This was true in 1.0 release of Java, but with todays JIT's the speed difference is small. I can point you to numerous sites, but at the end of the day it comes down to good coders. Your experience must be with some bad coders.
2. SWING is slow. This again use to be true with 1.18 + SWING and 1.2x JVM's the 1.3 and 1.4 have increased SWINGS speed considerably.
3. JAVA takes up too much memory. Yes it is true that the base JVM can take around 5-16MB of RAM per JVM instance. But with todays systems, on a lot of applications that isn't too bad. Now the core issue is that it takes up that amount for EVERY JVM that is used. So to your point: If I launch a Java calculator program, and then launch a Java notepad, I will have lost around 10-32MB of RAM in just JVM's. This is currently true, however it is being addressed and should be solved with the 1.5 release. Once this is done, then it would be possible to have ONE JVM running on the system for all Java applications. The JVM could launch at startup and then even the inital load times would be greatly reduced. I believe that this is the way Apple is handling Java (Can't confirm it though).
So, when this issue is resolved, running Java on a machine could mean only giving up a maximum amount of 16MB of RAM for the JVM and the rest for the application. To be honest that is what most Java programs are doing today. Most run as an application server and run Servlets and JSP's all day long.
Another poster mentioned that you use the correct tool for the job. I agree, but I will add that the issues for not using Java for speed has and is going away. The reasons for not using it for memory are going away on most computers.
We do agree on one point. Most people do have computer processors far greater than they need.
Lastly, if you are having so many issues running Java apps on your system you should look at newer JVM's. They make a huge difference.
The more I learn about science, the more my faith in God increases.
Why do I have a strange urge to try and embed it in an applet?