Slashdot Mirror
Creating Applications with Mozilla
On the first and most obvious level, the book is just the typical, thorough treatment of the important APIs that we've come to expect from O'Reilly. There are chapters addressing all of the important layers of the Mozilla platform and plenty of examples that show you how to customize the platform. Some may want to change the icons and others may want to add more robust features. The range of possibilities is surprising and coders are creating one-to-one communications enhancements, add-on widgets, and even games. There are certainly some things missing, and some areas that could use more detail or more complicated examples, but the book is already 454 pages long.
On another level, this book is also one of the first finished documents that explains what the Mozilla group has really been up to for the past five years. Some have abandoned the project, and others have attacked it as fundamentally misguided. This book shows why it took so long by demonstrating all of the cool features added during the long march to a new, thoroughly extensible architecture.
Are the results enough to justify the time and the effort? Some note that the features may be a bit overhyped, because building your own browser with the Mozilla API is like making a pizza with $15 and a telephone. While there's a large part of the book devoted to the work you can do to change the look and feel of the buttons on your browser, the book and the project offer much more. The Mozilla project is one of the biggest threats to simple tools like Visual Basic to come down the pike in some time. The various layers offer many ways to provide good, customizable interfaces to databases, the web, and much more. I can see how many corporate development shops may want to start making Mozilla the platform for a license-free front-end, simply because it's a straightforward tool without extra costs or restrictions.
At the most abstract level, the book is a great way to get a taste of modern software development. Computer scientists sometimes fix problems by adding more and more layers of indirection. This may not solve anything, but at least there are hooks for a real solution to use some time in the future if some one ever does figure out how to make the box do it. The Mozilla browser is one of the most extreme examples of this philosophy to ever emerge. Emacs was something special, but this is even more insane. Everything can be changed around by rewriting some XML and Javascript and most people don't need to juggle the pointers in grubby C to do amazing things. I realize it's not as beautiful as Lisp to some, but it's got a clarity and level of abstraction that's stunning to behold. Lisp was just procedural, while XML is more like logic programming.
This relentless customizability embodies one of the deepest reasons for the success of open source. Technology is inherently complicated and the only way we can use it is if we can look under the hood. You can say all you want about CVS trees and bazaars filled with competing code, but opening up the interface is one of the most powerful themes of open source. It's not about teaching people to build their own VCR or PVR from scratch, getting the VCRs for free or even debugging the VCR's source code -- it's just about making them easy enough to program.
The book illustrates how Mozilla opens up the API to create a relatively easy language for people to use. The real open source is not the C in the tar ball, but the XML interface spelled out in the book. Many people feel that the most important thing that the first browser designers did was make it easy for people to see the HTML tags marking up the document in front of them. The new Mozilla takes this transparency to a new high.
If you look at the book at all of these levels, you can see that this is one of the most important documents to emerge from the open source community in some time. At first glance, it's just another set of APIs for us to wiggle. I realize it's not fair to credit the Mozilla team or the book authors with creating the browser or XML ex nihilio -- they just jumped on some of the most popular bitwagons propagating across the Net. But the result is a stunning completion of a very important and cohesive vision. The book doesn't crackle with bleeding-edge novelty, but shines with the certainty of a job well-done.
Peter Wayner is the author of Translucent Databases , Disappearing Cryptography , and a number of other books. You can purchase Creating Applications with Mozilla from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
It could be a stand alone app that uses mozilla as the core functionality. It's my understanding Mozilla runs on almost every available platform where IE is windows specific (the mac version is nothing like the windows version).
That being said I run mozilla on mac os 8, 9 & 10, linux, solaris and windows. I'm not sure what the problem would be.
I would not call it a web application in the common interpretation of the word. The Mozilla framework would be used to create a client/server application. It would be more similar to creating a new alternative to (X)HTML.
Besides, Mozilla technology is available on most important platforms by now.
Stop the brainwash
Mozilla just becomes a toolkit and VM to run applications. Think of it like Java. Can you run a java app w/o the JVM? No. It's not executable without it.
It seems Mozilla is working closer and closer to being an OS than just a browser. Kinda funny if you think about it, where MS has windows which was supposed to be an OS and is now including a browser.
-
ping -f 255.255.255.255 # if only
Let's see... can I embed IE into my web app?
Nope.
Can my IE web app run on almost every platform out there?
Nope.
Can I modify IE in case I need additional functionality?
Nope.
There's the tip of the iceberg in differences...
Department of Homeland Security: Removing the rights real patriots fought and died for since 2001
Not sure whether it will catch on, but it's nice that they make it easy for other developers to benefit from all the work that's gone into coding Mozilla.
This is one way in which you just know that the Mozilla developers are at the top of their field(s) -- deciding to go with XML full-fledged (several years ago, too) was one of the greatest decisions they've made so far. The XUL interface, which is basically XML-based at its core, is about as flexible as one can get with the UI experience.
Furthermore, and of particular interest to someone like myself, the XML format offers a number of advantages for computational physics: clear markup of input data and results, standardized data formats, and easier exchange and archival stability of data.
I will definitely use a few dollars of grant money to purchase this book and keep it in the labs for all to read and enjoy.
Department of Physics and Atmospheric Science, Dalhousie University, Halifax, N.S., Canada, B3H 3J5
How come Lisp become 'just procedural'?! Do u have any idea baout what u r writing?
Ugg you got modded insightful. I better clarify before I get modded down:
This article is about the mozilla application framework. The application can be a stand alone application! This is not some kind of "mozilla only webpage."! This is just a method for creating an application that uses parts of the mozilla codebase, or more appropriately (though you and the mdos don't seem to understand the meaning of this) the mozilla application framework.
--
WHO ATE MY BREAKFAST PANTS?
this could catch on. Why on earth do you think they were so hot to kill the browser market for anything but IE?
Hint: It was *not* to simply have the most popular browser that they made no profit on.
KFG
mozdev has it for free
In true open source fashion, the book is also available in online form at http://books.mozdev.org/chapters/
An example of this kind of thing would be Komodo, an IDE for Perl/Python/Tcl/ development.
I seem to recall that some use MSIE as a component architecture to develop generalized applications in much the same way, but I can't think of any examples of this right now.
Isn't so much about standards, it's more about de-facto standards and their general tendancy to change. I couldn't see devoting 5 or 6 months to develop a custom application specifically for Gnu/Mozilla when one year down the road they may decide to alter the XUL "standard" and totally screw me.
This is why stuff like TCP/IP and "C" took off, because they were in the hands of a standards body who were responsible and considerate of issues like this.
The Gnu/Open Source community needs to take into consideration that since they are working their way into the mainstream they *must* begin to be more proffesional and intelligent in matters of "standards" or they risk alianating the commercial development community.
That would be a serious mistake on their end, serious indeed.
Warmest regards,
--Jack
Wagner LLC Consulting Co. - Getting it right the first time
I've been developing some apps using Mozilla at work. I've been really happy with it, frankly. The GUI development couldn't be easier, you can create relatively complex widgets with it easily, and, with the exception of any compiled XPCOM objects you may have, it's cross-platform. We picked up a copy of this book as well, and it's quite good. I don't know if it's the wave of the future or not yet, but I rather hope so, because it would make my life a lot easier (especially when I have to write Windows apps; I'm not a big fan of the complex IDE tools Microsoft provides).
Good troll attempt! I'll give you an A for effort!
Let's see... can I embed IE into my web app?
Nope.
Yes you can. I've done it before, and I currently use three different programs with IE integrated.
Can my IE web app run on almost every platform out there?
Nope.
You're right about this one, but for most commercial apps, hitting 99% of the users is pretty damn good. You can't please all the people all the time.
Can I modify IE in case I need additional functionality?
Nope.
Yup, you sure can. I run a customized version of IE for a few special projects.
Oh yeah, and this has all been true for several years now.
So, 2/3 were flat wrong, and the third one was pretty irrelevant. All in all, I gotta say this was a *very* professional troll. Blatantly wrong, and intentionally inflammatory.
You can browse different categories of Mozilla projects at MozDev.
I know this is short notice, but I'm going for dinner with one of the the authors tonight in two hours time, and then going to his talk with the Internet Society in Trinity College Dublin (Ireland). The details of the talk are here.
For a group of people which rely on so many open standards (and indeed, complain when companies don't use them!) I've yet to see little progress here on ensuring XUL remains an open standard. Which is a pity, because otherwise it has little to recommend it, no matter how extensible it is.
Also, does anyone here know anything about performance issues? Visual Basic nowadays is fairly reasonable for certain aspects of enterprise solutions, but if this is anything like Mozilla I'm not sure I could recommend it as being a good platform for applications.
Jon Erikson, IT guru
Good examples would be Oddpost, an email app that launches from the web, and RhymBox, a Jabber client.
Note that I've spoken to the froods who did both of these projects, and they've been constantly hitting the wall in terms of what IE can do. RhymBox now uses quite a lot of ActiveX code in order to work around the general lameness of using DHTML .hta files for the ui.
In short anywhere which requires a web-oriented application (preferably cross-platform) would do very well to evaluate Mozilla as a development platform. I expect database and server-side apps will ship in due course with applications based on Mozilla to do form design and other administrative tasks in a cross-platform manner.
Anyone planning to go to this probably knows already, but Brian King is giving a talk on Mozilla in Trinity College Dublin tonight. More details at http://netsoc.tcd.ie/events/0203/mozilla.php
-- Proud descendant of semi-nomadic cattle-herders.
But have you dabbled with web design? If the answer is yes, then you can write Mozilla apps. It's due to this fact that it's so easy to write patches for Mozilla. XUL (which if you know html is easy), CSS and JavaScript are all you need to know.
You could well be a programmer with Mozilla, and never know what a pointer is.
Well the subject of my comment pretty much gives away the comment.
ActiveState http://www.activestate.com (The Perl,Python,PHP,Tcl people) have a great IDE application written on the Mozilla engine called Komodo, it's up to version 2 now and certainly worth checking out.
Now if only ActiveState would just open source it, after all it's base is open.
Point two is not only correct, as you yourself admit, but is most certainly not irrelevant as you claim. Between desktop boxes, PDAs, embedded systems and non-Windows PCs, IE does not have a 99% market share. I think that perhaps you are confusing a particular segment (commercial retail) of commercial software with the universe of commercial software.
Point three is probably correct despite your denial. I'm fairly certain that the previous poster was referring to mshtml.dll and not IE itself. While IE provides a powerful and flexible toolkit, the fact remains that if there is a need to alter the core behavior of the toolkit there is no method for the developer to do so aside from petitioning Microsoft to change the behavior. This is not the case with Mozilla.
i have to say that i have converted a bunch of cgi's that deliver HTML to cgis that deliver XUL and provide RDFs. the interface is awesome ... so many things you cannot do with IE alone (unless you cookup some ActiveX)
... i hope an activex control for IE is around that will allow IE to use XUL
it was rough in the begining since i had people that were not using mozilla and even now some people just use mozilla because they have to.
but the power of the lists, tabs, etc are awesome compared to having to write javascript/layers/etc crap that takes more effort than the cgi environment to code.
i love it
members are seeing something, your seeing an ad
It's named OEOne
Very Insightful
There are a couple of very interesting examples developed using this technology out already:
- OEOne, a complete desktop environment.
- Kimodo, a python and perl IDE.
I myself am working on a Bible program that will run, locally, under Mozilla. This is probably the future of desktop application development for most stuff."He who would learn astronomy, and other recondite arts, let him go elsewhere. " -- John Calvin, commenting on Genesis 1
What is doubly amusing is that when Microsoft attempted to kill (perhaps did kill) Netscape, they did so because they were scared the browser would turn into a platform that would let you write kickass apps making Windows irrelevant. In a way, this became a self-fulfilling prophecy, as if Netscape hadn't been taken over by AOL and left to do its own thing, would Mozilla (a platform as well as a browser) exist today?
I doubt that one day all desktop apps will be written using Mozilla. But it's an intriguing possibility, I look forward to the GRE with much interest.
As pointed out in a discussion a couple days ago, this RedWolves2 guy is embedding his associates ID into his amazon links, in order to make a profit. And he's not telling anybody about it. He's done this a dozen or more times, and seems to be using Slashdot primarily for posting these Amazon ads. Moderators don't seem to be catching onto why this is a bad thing, and are modding up his posts. A user named Schlach had a couple great posts about why this is sleazy behavior. One's here, and the followup is here. Both are worth reading. Incredibly, I've been modded down for pointing out this questionable behavior on the part of RedWolves2. Read Schalch's comments and judge for yourself.
I'm generally "Interesting," "Insightful," and even "Funny" here. What the hell happens to me at parties?
Eventually Mozilla will become emacs.
Secession is the right of all sentient beings.
komodo from activestate is a stunning example.
War is necrophilia.
Hiyas, Pave! Good trolling!
Folks, this is a rip of the preface of the book.
Have a look for yourself and then mod this troll down.
~Dalcius
Rome wasn't burnt in a day.
I've been developing a Mozilla-based application component since August 2001. It's an HTML-rendering MOO client, and recently I've been pouring some 90% of my free time into working on it.
75% of that 90% of my free time lately has been updating the application to newer standards which have come into place since August 2001. For example, the Navigator/Mail/Editor/Chatzilla options used to be on the 'Tasks' menu in Mozilla, and were moved to the 'Window' menu around 1.0rc1. Bang, suddenly my application stops working properly, and less importantly, stops being a friendly component which works like all the others. A patch from a friend moved just about everything over to the 1.0rc1 way of doing things, and all was fine. Not everything worked flawlessly, though. The 'MOO Client' menu option didn't have an associated key visible, and the 'Window' menu inside MOOzilla didn't have any visible keys. The menus inside the application had long since stopped graying-out/disabling properly depending on what you have selected in the window. Many hours of last weekend was spent fixing these problems by conforming to new command handler expectations, and so on. (Where 'new' means 'changed since 0.9.6'. ;))
XUL is a wonderful tool. However, it runs dog slow on OS X. You don't have to take my word for it, just look at the Pheonix project. Pheonix is available for Windows and Linux, but not for OS X. Why? Because Chimera exists for OS X, which is faster (I'm using it right now) and integrates with the OS better. But... it doesn't support XUL. That's why it's faster. So where is my Mozilla application left? Stuck in the massive Mozilla suite when it's run in OS X. Mozilla, at startup, uses over 120 megs of RAM on my TiBook. Thank God for good VMs.
When initially writting MOOzilla, the XUL documentation was shit. The only place to go for any idea of how things really worked was deep inside the Mozilla source. And sure enough, this worked. The official XUL documentation at that time had sections which trailed off in 'blah blah blah' often because someone got bored of writting. I specifically remember it once read 'This is very important because blah blah blah'. Arrrg! How frustrating!
Mozilla is a powerful application development environment. XUL is a wonderful tool. Books like this one are going to make the world a better place for Mozilla component developers. And more cross-platform software developed with Mozilla makes the world a better place for users. Now... if only we can somehow apply this book heavily to the head of people who don't want to download Mozilla to try out an application, because they don't want to use it as a web browser. *sigh*.
But is the book any good. All I got from the "review" was that the reviewer thinks Mozilla is cool. What about the book? Was the book good? Was it well written? What did the reviewer like about the book, not the subject, that warrants a 9? Why not a 10, what didn't he like about the book?
LoRider
You are not alone. This is not normal. None of this is normal.
And here I thought he was one of the knights who say "Ni!"
"I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
The book is good and interesting, but it reminds me another book, Programming Jabber: a lot of examples in the book, and no available examples in real life (besides Jabberd itself).
Less is more !
I think you are so seeing the potential. What *is* needed is an HTTP-based "GUI Browser". HTML-based browsers don't cut it. If Mozilla can fill this need, great.
Where the contention comes about is in how fat the client should be. IMO, most or all the functionality should be on the server, with the browser being Turing-dumb. (I drafted an XML protocol called SCGUI to do just this.)
However, some people and applications are going to want/need client-side scripting. If it gets to be too much client-side scripting, then you have essentially created a client-server application. That is probably what Mozilla should *not* target.
I guess what I am trying to say is that there is a need that Mozilla can fill and that I hope it does not get carried away in an Emacs-ish way.
That niche is an HTTP-friendly GUI browser with *optional* scripting capability to have *some* local Turing-complete application programmability sprinkled in. IOW, get right what HTTP+DOM+JavaScript could not get right.
But, if they make it a fat-client client-server tool, then slap them with a wet Visual Basic box.
Table-ized A.I.
Dude-- read the review. Here are a few sentences from the top: On the first and most obvious level, the book is just the typical, thorough treatment of the important APIs that we've come to expect from O'Reilly. There are chapters addressing all of the important layers of the Mozilla platform and plenty of examples that show you how to customize the platform. Some may want to change the icons and others may want to add more robust features. The range of possibilities is surprising and coders are creating one-to-one communications enhancements, add-on widgets, and even games. There are certainly some things missing, and some areas that could use more detail or more complicated examples, but the book is already 454 pages long.
Sounds like he talks about what can and can't be done with the code samples and even a bit about a few of the individual chapters. He just didn't do one of those boring Slashdot reviews that goes through each chapter one by one. I can get the chapter breakdown from the book's website.
And if you ask me, knowing what to do with the XML is pretty important. If the Mozillians are smart, then that means there's something of value int he book. I really don't want a well-written, witty book about how to write assembler code. Dis
Yeah. You call the dll's directly. You can use any of all of the functionality in IE, and yes, it is distributable. I don't remember the names of 'em now, but there are several to use. And yes, you can customize it however you'd like. You can do a web browser window, do whatever buttons you'd like, however you'd like. I have one tool which is does something automatic, and doesn't even have a GUI. You can absolutely embed and customize it. Check out the details at MSDN. Hell, I'm looking at Quickbooks 2002 which is built around IE. They just use it for the rendering... no actual browsing per se.
I use a customn app that I wrote that is completel automated using the XML object that comes with IE. You don't need the source since you have access to every possible property/method in every DLL, and they're all documented. If you have to muck with the source, that's because the program itself doesn't work, or has a shitty API. IE works and has a very extensive API. Has for years.
And no, of course you can't use it on Solaris. But, I'm not aware of a whole heck of a lot of products that would need to be ported to Solaris (Quickbooks for Solaris? I don't think so.).
So yes, you are completely wrong.
This isn't even close to a book review. He does nothing but glower over how great Mozilla is (which we all agree on), but says nothing about the quality or content of the actual book.
The book itself *IS* good (at least that which I have read so far). You'd never be able to tell from this review though....
I laud Mozilla for going down this road and it is clear to me that the core developers for Mozilla are a step above your standard programmer. Some accuse Mozilla for not following a method that would create "standards" for their XML GUI description language, but I have found that the successful "standards" usually follow already adopted and reasonably mature technologies. You do not know how you want to design something until you have done it, used it, and given it to other people to play with. Only after an application has grown sufficiently to include all the thousands of unexpected details is it sufficiently mature for people to talk about standards. For example, I consider the EJB specification's largest failing is that they tried to standardize it before it was actively used for a couple of years. Only now that we have some mature app servers do we really have an idea what needs to be in the core EJB specification. If EJB had followed this road, maybe application developers would not need to use vendor specific code for the critical parts of the functionality. Like OO, the mantra of "standards" seems to be more of a marketing tool to get Fortune 500 companies to cough up millions of dollars than something that really influences how sophisticated and successful applications get developed.
I have my own questions for the Mozilla team. How do you deploy "overrides" of existing configurations. Suppose I want to deploy a "batch" of changes that I want to turn on or off. Is there a way to create configuration "layerings" in XML files so a group of data specifications can be conditionally included from a set of external files? How much scripting is allowed in these files? If I want to write conditional code for specifying a color (such as a color choice per day of the week), is there a way to write scripting solutions for that need? Of course, I could read the book but I am lazy and I suspect that it would not give a full answer.
*sigh*
All that IE does for Quicken is allow Quicken to use it as an HTML renderer. This is much different than Mozilla which can create a standalone application. The Quicken developers had to use C++ of VB or whatever and embed the MSHTML control into it. Mozilla does not require anything in addition to the package itself to create a new application. So even though this isn't necessarily new, it's definitely a lot more than IE can do on it's own. Plus you can embed Mozilla into apps like Quicken as well. Topstyle does a great job of integrating IE and Mozilla side by side using this technology.
Dissolve... Resolve... Evolve...
we also now have a very inexpensive GUI on the clients. Had the makers of the XTerminals been more realistic, this wouldn't be news because we'd already have thin-ish clients with a GUI interface.
There are MANY places where thin-ish clients are far more practical then thick clients. Especially when MS Windows is what's running on the thick client....
There are many places for thick clients also.
IMHO.
LoB
"Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
How close is this Mozilla thing to supporting that?
I've read several chapters of this book and I'm trying my hand at Mozilla app development. I'm mainly interested in it for "better" web applications. HTML was never designed for that kind of thing, and I'm frankly tired of it being used for such. Mozilla+XUL can make applications that load like web pages but whose interface is more like traditional desktop applications. Rock on!
I really DO believe that Mozilla has a bright future in this regard. It provides some great tools. I about wet myself when I discovered the Javascript Debugger! As the article says, it will provide a totally free/Free way to deploy custom applications.
It's also a potent tool against IE's monopoly. If there's one thing that can cause people to switch from IE to Mozilla, it's applications that only work in Mozilla! I used to support the "Best Viewed with Any Browser" campaign (which is still appropriate for pure information) but I have since realized that because Mozilla is Free, open, and cross-platform, there is no need for anything else! I now encourage people to develop web-based applications in XUL.
I do have a few small gripes with it. Textboxes don't wrap like they do with HTML's "wrap=soft" attribute. That's bad. I asked in a newsgroup and was told that this functionality would be in Mozilla 1.2.
Also I was hoping to embed an HTML editor in my application, so that people could post HTML in their comments and have a fancy editor for them. To my dismay, it appears like the HTML Composer can ONLY be embedded in local chrome:// apps, not in those served by HTTP. Anyone know a way around this?
Overall though, Mozilla kicks arse! I think it has a very bright future!
For remote access, all the server has to do is send XML data to Mozilla. Also, Mozilla natively supports the SOAP API, so it can access any SOAP data source. Cool, huh?
;-).
It's a little different if you are talking about accessing client-side data sources. Mozilla/XUL is (kind of) a virtual machine (VM), meaning it doesn't intrude too much upon the client's OS. But, XUL/XPCOM has bindings for all kinds of programming languages, such as C, C++, Perl, Python, Ruby, and the list keeps getting longer (Good intro here). Thus, on the client-side you can use the database capability of any of these to talk to the Mozilla elements. I'm sure it wouldn't be too hard to whip up just a little communication between Mozilla and ODBC
I would like to relate a recent experience with NETSCAPE 7.0. Please excuse two paragraphs or so of background information...
But I digress... So back to *N*E*T*S*C*A*P*E* I installed Netscape for my mom, because Internet Explorer is trash. Netscape, in my opinion, is lacking in many areas (such as usability), but I'll classify it as software, rather than trash. So I installed it. The install went along pretty smoothly and before I knew it, I had Netscape launched. The new graphics are MUCH nicer than the extremely crappy ones in Communicator 4.x. But the initial screen was SOOOOOO cluttered!!! Buttons and tabs and side bars EVERYWHERE! As an experienced user of computers and web browsers, I couldn't hear myself think, so to speak, in all this optical noise. I immediately turned all that crap off and modified all the settings to my liking, so that my mother, who has much less experience than myself, would actually be able to use the damn thing. And then it happened. The next time I launched Netscape, everything locked up and the disk started crunching and grinding away like there was no tomorrow. Even the ctrl-alt-delete window took forever to show up. I ended up forcefully shutting off the power, because I couldn't even log out. (Yeah yeah... File a bug report--but do you HONESTLY think that my mother knows what a bug report IS, let alone knows how to file one?!!) And this is where the background information on XP comes in... I guess it REMEMBERS what made it crash and when you reboot it (or log out and log back in) it does it over again, consequently putting itself in the same situation and locking up again. That's what happened. Whenever I logged into my mother's account, the whole computer became so unresponsive (from the grinding and whatnot) that I couldn't even open up the huge, cumbersome Start menu. (Mafiasoft. Where do you want to pay today?)
I noticed that the other account, that I had originally set up for her out of the mere habit of always giving myself three or four accounts on my BSD boxen, still worked fine, so I logged into it, created yet another new account, moved all her files over, and deleted her original account. Oh yeah, and I removed Netscape and purchased a copy of the newest Opera 6.x for her. Sure, its initial screen is a bit cluttered and I have a few complaints about the increasing complexity and proliferation of seemingly unnecessary features (that other people probably want, just not me), but it's small, fast, and it WORKS. Extremely well, I might add. (It's what I am using right now under FreeBSD with Linux compatibility turned on.) Now she's happy as can be... And I know for a FACT that I will not buy a computer with Windows XP. And I am pretty disappointed with Netscape once again (not so much for the crash, but very much so because of the clutter), as I have been for several years. (Yes, I will continue trying it from time to time, because somewhere deep inside, I believe that it will BECOME a very good, reliable web browser. I just wish it'd become as SMALL as Opera (3 megs or so) and as fast. Netscape is very, very slow.)
I hope if any Netscape developers are reading this, that they'll take this as constructive criticism rather than as flamebait. Oh yeah. And YES, I know the Gecko engine is found in Galeon and several other browsers.