Mozilla's Major New Roadmap 481
kerz writes "mozilla.org today released a new version of it's famed roadmap, this time with some pretty major changes. First and foremost, they plan on ditching the large Mozilla suite in favor of Phoenix and Minotaur. Secondly, they have plans to change the milestone cycle to allow for more time to fix the Gecko layout engine to be smaller and more efficient. MozillaZine has the scoop..."
Makes Sense (Score:4, Insightful)
Re:Makes Sense (Score:3, Interesting)
I have not used mozilla browser ever since phoenix 0.5. And I have been using the phoenix nightly builds.
I use phoenix on linux/windows/solaris, I haven't restarted phoenix on my solaris box for days/weeks. Its fast, sleek, and has a very small memory foot print as compared to the lizzard.
Some of my concerns with phoenix though are
Re:Makes Sense (Score:2)
I saw Phoenix as a very interesting and promising fork until development has essentially stopped. To see the Mozilla folk pick it up again is a relief.
Re:Makes Sense (Score:5, Informative)
I've been using the April 1 build all day today... heavily... and it's been holding up like a champ. If I were going to compare this in terms of version numbers, I'd call it the
Re:Makes Sense (Score:3)
One Gripe about Phoenix/Mozilla (Score:3, Interesting)
Does this have anything to do with mouse gestures? Can I fix it? Lately I seem to have better luck if I drag the link to the right before dragging it up to
I agree.. (Score:5, Insightful)
I don't personally I have a problem with the size of mozilla, but since I only use it for browsing, it will be really nice to get rid of the rest of this monolithic application.. but to have it available for when I want it.
The path it has set now reminds me of the KDE applications. The PIM/Mail suite has a great deal of functionality.. but you don't have to load it just to browse a web page. (Though many would argue that Konqueror also tries to be all things to all people..)
On Linux.. Mozilla and Phoenix are the way to go.. though on OS X, Safari is a really nice browser.
Re:I agree.. (Score:3, Interesting)
I disagree. They took some of the ideas from Communicator, but dropped some of the others which I found important. For instance, communicator was very fast in it's own right, communicator's editor is better than Mozilla's, etc, and the interface was quite clean and elegant.
You've got to be kidding. KDE is farther gone than Mozilla. The bloat and lack of performance in KDE is i
Re:Makes Sense (Score:5, Interesting)
Re:Makes Sense (Score:3, Funny)
Like Notepad?
Re:Makes Sense (Score:4, Funny)
scripsit gspira:
:wq
The basic no frills standalone HTML editor (Score:5, Insightful)
And if people would stay away from Frontpage and the like, the world would be a better place too.
Re:Makes Sense (Score:3, Interesting)
I think he had in mind a world in which anybody could write and publish "annotations" to every web page (I think the old mosaic tried to support this). Right now there are several "server-side" applications that let you do this (blogs, wikis, etc...). Most people don't need or want an html editor, and with modern technology an html editor is mostly unnecessary for people to publish on the web.
Re:Makes Sense (Score:5, Funny)
Re:Makes Sense (Score:3)
Re:Makes Sense (Score:3, Insightful)
Re:Makes Sense (Score:4, Insightful)
I installed the browser and mail on my machine that I use for mail, and just the browser on my machine at work. After years of waiting, all the functionality I need is complete, close to perfect even. I've got tabs, popup, image, and spam blocking too!
If you don't want one of the other components, don't #@$#%ing install them! (And quit yer whining.)
Why would I want to go back to another half finished browser?? I think this decision is a mistake, and just serves to lose momentum.
I think a better idea would be to work on making mozilla more modular and making other performance tweaks. Why reinvent the wheel again?
A day late (Score:5, Funny)
Re:A day late (Score:3, Funny)
Right. And what a shame I wasted all my mod points yesterday.
Mozilla?? (Score:4, Funny)
Re:Mozilla?? (Score:2)
Re:Mozilla?? (Score:5, Funny)
There are wormholes in IE? Can I use these to go between work and home faster? Wow, this will really increase my productivity. I can use that extra 1 1/2 hours each day playing the new Zelda.
-prator
Re:Mozilla?? (Score:5, Funny)
Sadly, in most corporate environments, all wormholes only lead to the boss's office... or to the marketing department meeting.
Re:Mozilla?? (Score:4, Funny)
Nah, those are black holes.
RC
Re:Mozilla?? (Score:3, Funny)
Yes, using the wormholes in IE you can run proigrams on your work computer while you're at home. It works just like SSH without that pesky authentication junk!
Re:Mozilla?? (Score:4, Funny)
here ya go (Score:5, Informative)
1.Switch Mozilla's default browser component from the XPFE-based Navigator to the standalone Phoenix browser.
2.Develop further the standalone mail companion application to Phoenix already begun as Minotaur, but based on the new toolkit used by Phoenix (this variant has been codenamed Thunderbird).
3.Deliver a Mozilla 1.4 milestone that can replace the 1.0 branch as the stable development path, then move on to make riskier changes during 1.5 and 1.6. The major changes after 1.4 involve switching to Phoenix and Thunderbird, and working aggressively on the next two items.
4.Fix crucial Gecko layout architecture bugs, paving the way for a more maintainable, performant, and extensible future.
5.Continue the move away from an ownership model involving a large cloud of hackers with unlimited CVS access, to a model, more common in the open source world, of vigorously defended modules with strong leadership and clear delegation, a la NSPR, JavaScript, Gecko in recent major milestones, and Phoenix.
6. ???
7. Profit!
Ok, I admit to adding 6 and 7.
Re:here ya go (Score:5, Funny)
7. Profit!
Ok, I admit to adding 6 and 7.
As digitally altering media contravenes the stated principles of this medium, the above poster has been sacked...
Re:here ya go (Score:3, Interesting)
I have to wonder what "performant" means. It is proof that marketing types were involved in the writing of this roadmap document.
Re:here ya go (Score:4, Informative)
I have not been able to find a definition of the word. The closest I've found is from a google search (from a cached page [216.239.57.100]):
First 404!!! (Score:2, Interesting)
Re:First 404!!! (Score:4, Insightful)
Finally! (Score:3, Insightful)
Re:Finally! (Score:2)
I had Pheonix for a while but couldn't put up with the lack of certain features (image/cookie blocking, etc etc etc).
Here's to a full-featured, stand alone browser!
competing with camino (Score:2, Interesting)
Re:competing with camino (Score:5, Insightful)
I imagine that people would use Phoenix on the Mac if they wanted to have that nice "one browser on every platform" feeling. I know that's why I sometimes use Mozilla on my Mac.
All this means is that Mac users have even more choice when it comes to browsers, and to me that's a good thing(tm).
By the way, Phoenix already exists [kmgerich.com] for the mac (sorta).
This is a Good Thing, IMHO. (Score:4, Insightful)
Re:This is a Good Thing, IMHO. (Score:5, Insightful)
And if you don't want all that 'bloat', then use the use the net installer and install only the browser portion.
Re:This is a Good Thing, IMHO. (Score:3, Insightful)
Plus, it would be nice to be able to get fixes for the mail/news client without changing the browser portion at all. What really makes Mozilla bloated is that there's no reason for all of it to be one program, rather than a set of independant programs that can invoke each other.
Re:This is a Good Thing, IMHO. (Score:3, Informative)
As for upgrading things seperately. Yes, you could do this already assuming anyone had the time to maintain the mail/news and browser components seperately. Unfortunately they don't
Re:This is a Good Thing, IMHO. (Score:3, Insightful)
For the download, they could offer the engine separately from all of the applications, and they could have each application have a version with comes with the engine (download this one if it's your first mozilla application).
You d
Re:This is a Good Thing, IMHO. (Score:5, Insightful)
The corporate market is where 80% of the world's PC installs occur, and Mozilla.org has never shown the maturity to support that market.
sPh
Phoenix for Mac OSX! (Score:5, Interesting)
They're finally going to support Phoenix on OSX!
This is a big win for the Mac community imho. Camino is great, but there are barely enough developers to cover the front end, the main body of the Mozilla project being behind a cross platform Phoenix project is a Good Thing?.
Re:Phoenix for Mac OSX! (Score:5, Insightful)
It might also be detrimental to Mozilla on the Mac. Right now, it's basically Camino vs. Safari. If it becomes Phoenix vs. Camino vs. Safari, the Mozilla camp becomes split.
Re:Phoenix for Mac OSX! (Score:5, Interesting)
Re:Phoenix for Mac OSX! (Score:2)
Happy to hear it (Score:5, Interesting)
Re:Happy to hear it (Score:5, Interesting)
Honestly, the change is mostly cultural and social - a separate development community and process, and a dedicated user community were integral to Phoenix's success. Mozilla has been too large and faceless to really bring the user community in close touch with the developer community in the same way that happens in the Mozillazine Phoenix forums. And the development process seems less nebulous, less roadmap and process driven, and more feature and stability driven.
My only hope is that integration of Phoenix into the Mozilla main project effort doesn't kill exactly those things we love about the project, but it's good to see all those thoughts on changing cultural elements of the Mozilla.org process up in their new roadmap - a breath of fresh air indeed.
Re:Happy to hear it (Score:3, Informative)
Two of your three problems are solved. Mozilla's mail client now remembers the last selected message in each IMAP (and POP too, I presume) mailbox, and you can configure it to send plain old text messages.
The latter feature has been around for a while; the former feature is relatively new but is definitely in 1.3.
So use Pine. Seriously. (Score:5, Insightful)
So use Pine.
Don't laugh! I still use it as my email of choice. I used to use Netscape, but when I got DSL and my Linux machine fully running, I just stuck with Pine. (I tried Kmail for a while, and Opera mail). People laugh at me, but when I am at home, I can view attachments fine with it. When I am away from home, it is a bit harder. But I don't have to download my email either. I can download PuTTY wherever I am, ssh into my box, and read my mail in about a minute. I did this recently while traveling in France. I also use fetchmail to gather my various accounts into one on my machine at home. Even on dialup I can check my mail pretty quickly.
People can't believe that I still use Pine, but it is light, fast, and easy. Of course, if access to my home machine is cut off for some reason, I have to use my ISPs webmail, but I LOATHE webmail. I don't have a compelling reason to use a GUI mail client.
Interesting... (Score:4, Interesting)
Re:Interesting... (Score:3, Informative)
Re:Makes some sense (Score:3, Insightful)
Mozilla could seriously do with some more large sponsors, though. It's just such a pity Apple didn't go for Gecko, for instance.
Sounds like a good idea... (Score:5, Insightful)
2. Faster
3. Less bloated
Less is more, in many, many things. Including software.
GF.
translation: they're spinning off mail/news (Score:5, Informative)
(Took me a minute to figure this out... Minotaur? Thunderbird? What?)
Sounds Great (Score:2)
Re:Sounds Great (Score:3, Insightful)
Death of Mozilla? (Score:2, Interesting)
Or perhaps this is just a way of disposing of the outstanding Mozilla bugs that no one is willing to fix? Just start a new product instead?
sPh
Re:Death of Mozilla? (Score:2)
Unlikely... Uncle Arthur's firm was a tax/audit/accounting firm. You're probably thinking of it's old sister firm, Andersen Consulting (now Accenture [accenture.com] -- for whose consultants this kind of language is second nature :)
In reality, this kind of talk is great when you're trying to sell change to someone, but when you've giving your product away you don't need to worry about your customer!
Re:Death of Mozilla? (Score:2)
I think its a great idea as long as I can upgrade to it without loosing my bookmarks, email, cookies, passwords etc.
Re:Death of Mozilla? (Score:3, Insightful)
In all seriousness though, I'm glad to see this new road map. IMO, this shows a lot of maturity and foresight on the part of the Mozilla team, and I applaud them for it. They realize the shortcomings of the approach they've taken during the last 5 years, and they have put together a solid plan for where they want to go from here. While this will undoubtedly cause some instability and uproar within the communit
wow (Score:4, Funny)
Seriously though, good idea. I'd love to see the whole Mozilla project turned into a Gecko app and everything else be plugins! Now that'd be cool!
Please tell me this is a late April Fools joke.... (Score:4, Insightful)
Phoenix is nice, the new standalone mail/news client will probably be nice as well, but I see no good reason for them to drop the application suite.
All this talk about how Mozilla is too big, too bloated, has too many features, etc., is a load of shit, IMHO. Unless you're trying to run Mozilla on a freaking Pentium 100 with 64 megs of RAM or something else antiquated like that, performance is fine. And if anything, there are still plenty of features that *should* be put into Mozilla, that the Mozilla.org folks refuse to implement, despite how many votes the RFE has, or how many people want it.
I say they should just keep developing Mozilla as it is, keep improving it, keep adding features, and let the people who want to work on Minotaur, Phoenix, whatever, do so.
Re:Please tell me this is a late April Fools joke. (Score:4, Insightful)
The RFEs you mention, will hopefully be things that are implementable as extensions to Phoenix - this will take some of the burden of feature enhancement requests off of the Mozilla.org folks and let others develop them independently.
Re:Please tell me this is a late April Fools joke. (Score:3, Insightful)
To your first quote I think they're saying that when it comes to UI design you need somebody in charge.. keeping things from moving back and forth pointlessly or getting schizo. They're moving to a decision structure more like other large opensource projects. You can still make changes, they'll just have to be approved and tweaked before making it into main builds.
To your second quote.. to many cooks spoil the soup. They don't need sudden floods of inexperi
Re:Please tell me this is a late April Fools joke. (Score:5, Informative)
Deliver a Mozilla 1.4 milestone that can replace the 1.0 branch as the stable development path, then move on to make riskier changes during 1.5 and 1.6.
(...)
the reasons for this new plan are:
1. Phoenix is simply smaller, faster, and better -- especially better not because it has every conflicting feature wanted by each segment of the Mozilla community, but because it has a strong "add-on" extension mechanism. (emphasis mine).
The idea is not to "drop" the suite, but to make it modular instead of hardwired.
I think it's lame to have them so intertwined... (Score:4, Insightful)
I know I'll loose points for this, but heck, even IE and OE/Outlook are seperate applications even though they mostly use the same core (MSHTML, Outlook uses the base OE libraries). Why can't Phoenix and Minotaur be like this? I love Phoenix. I use it almost exclusively at work, and pretty often at home. And, for the record, Mozilla is a dog on my home laptop, but Phoenix runs quite snappily. Modularity (more than just selecting components from the 'net install) is the way I think the Moz project should go, and I'm glad that they're heading down that path.
Re:Please tell me this is a late April Fools joke. (Score:5, Informative)
I beg to differ. On my other system, a 433 with 256MB of RAM, Mozilla is a pig. Pure and simple. It takes close to 30 seconds to load sometimes, and page rendering makes me feel like I'm back on 14.4 dialup. Contrast this with Opera, which loads in a second or 2, and renders pages as soon as they're downloaded (in fairness, I won't mention how fast IE is, because they cheat and preload most of the browser when the system boots
Now that I have an 1800XP, you're right, Moz is pretty zippy. But it's pretty sad that I'd need almost 2ghz of effective performance just to render some html.
I won't even talk about how long Moz takes to load on the Redhat box (p2-266, 256 RAM). Let's just say Galeon beats it by an order of Magnitude. Same renderer too, so just what's causing the delay? Oh yeah. Bloat.
Re:Please tell me this is a late April Fools joke. (Score:4, Insightful)
Safari jab? (Score:2, Interesting)
excellent, now that just leaves one problem left! (Score:2)
Re:excellent, now that just leaves one problem lef (Score:2)
They need to do this (Score:5, Interesting)
The ideal for Mozilla would be (IMHO) a browser, a mail client, a download client, an IM client, and a composer. Each should be replacable - I should be able to tie the browser into whatever download agent I want, have whatever email client I want be pulled up when I click on a mailto: link, etc.
I'd even go so far as to have a caching program that the browser and downloader could talk to (to unify the disk cache system), but then I already run Squid on my systems.
Of course, all the Moz bits could and should access the same DLLs (.so's) to keep the disk and memory footprint down.
Bloat is good... (Score:2, Interesting)
Why bloat is good, you may ask? The machines are reasonably fast these days, and users (ahem, let me say, just I) tend to spend significant time on the browser window, and mail window (and calendar, may be composer, etc). There is a common interface, one can upgrade everything at one shot (kinda like Redhat 8 and 9... you get everything updated). Makes life a little easier.
I would have com
ditch Mozilla suite? not what the document says! (Score:3, Insightful)
Deliver a Mozilla 1.4 milestone that can replace the 1.0 branch as the stable development path, then move on to make riskier changes during 1.5 and 1.6. The major changes after 1.4 involve switching to Phoenix and Thunderbird, and working aggressively on the next two items.
Make risky changes to 1.5 and 1.6 Mozilla. That doesn't sound like ditching to me. The post and the Mozillazine blurb miss the jist of the document.
Reaction to Safari? (Score:3, Interesting)
Some semi-random thoughts... (Score:3, Insightful)
What I'm most concerned about in the roadmap is the seeming focus on just the browser and the mail app. (Yes I realize the purpose of mozilla.org is not strictly to produce those apps but realistically, those apps are the main reason anyone cares about Mozilla) I use those heavily and anything that improves them is just ducky as far as I'm concerned. But just as important, and much more ignored IMO, are the address book and calendar. These are applications that almost everyone uses in some form. Obviously people choose other options (Outlook, etc) frequently but that's in part because the ones built into Mozilla are fairly bad. I use them because they are the only transparently cross platform option which is important to me. I use them all and if they were better I think many others might too.
Anyway , I see the browser, mail, address book and calendar as the four major applications that most users really need. The Mozilla browser (and I include Phoenix and Camino here) is great and is arguably the best on the market. But the other three apps have largely been ignored for some time. They have a basic level of capability but haven't been refined significantly in some time. I still have trouble sharing information with co-workers on different systems. I still cannot easily share data with the PDA of my choice. Mozilla could really make a lot of this stuff really transparent for users. I'd love to be able to not worry about OS for these four apps. Mozilla is better than halfway there but I'm not quite sure what this change in direction means.
Sweet! (Score:3, Interesting)
Why Phoenix is better (Score:3, Interesting)
Here's why [mozilla.org], according to the mozilla people.
This decision totally makes sense. At first I thought this wouldnt affect me, since I already use phoenix but of course this means phoenix gets the focus, which means faster development/bugfixes/features/etc...
Great news!
Resitance to change? (Score:5, Interesting)
I can only wonder at how a radical re-design this is going to turn out to be, from both a developer's and end-user's standpoint. The Mozilla project has, by all accounts, been an incredible success, and has been adopted by some major entities, eg. Sun, HP, IBM, Red Hat. By making this radical a change this soon after 1.0, do we risk alienating users and developers? I mean, now that people have gotten used to Mozilla, we turn around and dump something hugely different in their laps?
My fear is that commercial entities, along with the pro-Mozilla-the suite camp, will continue development on Mozilla Classic (the 1.4 branch), while the Phoenix folks work on NGMozilla...a fork.
Hold onto your hats, folks.
How to start a Mozilla spinoff project (Score:3, Funny)
Step 2: Find a name.
Step 3: Reach the 0.5 release, and develop a loyal following.
Step 4: Start to reach more users and get some name recognition.
Step 5: Come up with some sort of roadmap.
Step 6: Change the name due to legal issues.
Step 7: Declare 1.0 victory, and add yourself to the junkheap of other spinoff projects. Don't worry, though, there are more to join!
The name for Phoenix... (Score:3, Insightful)
Not a smart move and here's why (Score:3, Interesting)
I find it hard to believe that that a Phoenix based browser is going to reach a level of stability and adoption, any time soon.
(Someone has to say this)
This smack of developers looking at the technology and saying you know I could do better (yeah I'm guilt here as well). You know lets rebuild this and provide no migration path for existing applications and users. There must be a better way to do this with less risk and disruption.
Remember it's not always the product with the most technical merit that wins it the wins just look at IE.
Otherwise Microsoft is going to be very happy they will not have to worry about Mozilla any more.
Re:Not a smart move and here's why (Score:5, Insightful)
First, I'd like to address your "stability and adoption" comments. Stability - Phoenix is, at the very least, as stable as Mozilla, and anecdotal evidence I've seen suggests that it may, in fact, be far more stable. Adoption is certainly not an issue - it's not like mozlla.org is saying "Hey, our previous product sucked, try this new one!" - they're merely integrating similar, better technology into an existing product, and removing some of the not-so-great parts.
As for the lack of a migration path - remember, Phoenix is based on the same technologies (Gecko, XUL, XBL) as Mozilla, so development-wise, that all stays pretty much the same. The main difference for developers will be the new code ownershp model, about which I can only say "It's about time!"
So, while the "resistant-to-change, mozilla-loving" part of me agrees with you, the logical, wants-the-best-for-Mozilla part knows that this is the rigt path for the project.
Gecko, you can thank Safari (Score:4, Insightful)
Why is Gecko allowed to undergo fairly hefty changes? Easy. Apple's release of Safari brought attention to KHTML. Heck, Mac rumor sites had all but crowned Chimera (now Camino), based on Gecko, into the OS as the default browser. Then wham, out of left field, here's Safari.
Why did such a large company go away from what the open source community considered the gold standard, Mozilla and its technologies? KHTML was a smaller codebase than Gecko, and easier for a new project to make completely their own. That's right, there was a better open source alternative out there most people had never really thought about.
People started talking [dbaron.org] about KHTML, Safari, Mozilla, and Gecko. Apple managed to shine a new light on what had been seen as acceptable without question because of, get this, a lack of competition (!) in the open source browser community. Until the little man came on the scene, Mozilla and its Gecko brethren had a near monopoly on the "not-IE" browser market.
So the next time someone wants to know what Apple's given the open source community after taking BSD for the core of its new OS, you'll know what to tell them. Not only has Apple open sourced Darwin and checked their improvements back into KHTML, they've also provided a competitive peer for Mozilla and other open source projects.
Maybe; you may have missed my point, too (Score:3, Informative)
(Of course, I wouldn't want to work under those constraints, if I had the choice.)
I apologize if I misread the original post. Lately there has been a lot of "Apple picked KHTML, so Gecko must be de
A Good Move (Score:3, Insightful)
I think that mozilla had become a monster - a friendly one, perhaps (just look at the endearing pointy toothed grin on that red monster), but a monster all the same. And that kind of "lets pile everything together into a heap" integration is a pain for users who want to be able to pick and choose. There are lots of examples - both in the windows world and in the unix/linux... worlds.
In the windows world this is to be expected - one company wants to build one product - make you buy a new one every time any of the components changes. Given that most windows users are going to put about as much thought into selecting the products they buy/use as they do when they drive to macdonalds and have to choose between a "large" and "super size" fries, thats not unreasonable. (I'm not saying they're stupid - just that they're not putting any intellectual effort into their computing systems.)
But in the unix world, this grates on me Both KDE and Gnome seem to want to build bigger and burlier integrated thing-a-ma-bobs. Consider, for example, the rise of the desktop managers vs window managers. Or evolution - quite a nice mail client, an address book, a calendar and who knows what else - and I always managed to click on the wrong button and lose things. Or open office - nice spreadsheet - absolutely crappy word processor - but they come as a unit.
I would like to see XUL continued, and the roadmap looked like it was not being dropped - I think it offers lots of potential.
I'd also like to say in response to the person who asked "why chatzilla" that chatzilla might not be a requirement for most users - but it was probably a very good thing for mozilla - as chat has different requirements (in user interaction, display and in performance) than a browser does. As such, it has probably helped to shape the way mozilla has developed. Then too, I'm kind of tired of everyone saying that MIRC is IRC as though the only things allowed to exist on the network are windows applications.
Re:I think we've found what they are good at... (Score:2)
Re:I think we've found what they are good at... (Score:2)
I thought you said, "the Mozilla forks" I wonder how that could have popped into my head?
Re:browser bloat (Score:3, Informative)
If you're referring to the .rpm packaging, then submit a patch which breaks up the .rpm into more manageable chunks, or use the Linux net installer.
Either way it's not Mozilla's fault since it is as modular as the user or the install script tells it to be. If you choose to install everything including the kitchen sink you can hardly complai
Re:browser bloat (Score:3, Funny)
Some people like a big package.
GF.
Re:Ok... (Score:5, Informative)
My experience of Opera's stability is quite the reverse, however. Moz hardly ever crashed. Opera crashes a couple of times a month. The difference is that when I have a load of tabs open in Moz and it crashes I then have to hunt for all the pages I was looking at. With Opera it lets me continue from exactly where I was pre-crash. I now tend to not bother with bookmarks, just open pages that are interesting in a new tab, move that tab to the left of my current active tab and leave it there. For sites like /. I tell it to refresh the page every 15 minutes, and I can see at a glance if there's any more news.
Re:Ok... (Score:3, Informative)
As for Opera's "clean, intuitive" interface (another claim from your page), you might check out Matthew Thomas' claim that Opera is the only UI worse than Mozilla's [phrasewise.com].
Re:Ok... (Score:3, Informative)
The guy at phrasewise is, frankly, an idiot.
Speaking, btw, as a former Opera user who now uses Mozilla instead, on all platforms.
Let me review a few of his points:
This is to some degree debateable whether or not the under
Re:Webian, it's the future! (Score:2)
Re:Too risky! (Score:5, Insightful)
IANAMD (I am not a Moz developer), but I believe one of the problems is that some things in Gecko cam't be fixed without redoing the architecture. By every account I've read, most of the Gecko codebase is a mess.
we should expect that after 1.7 Phoenix's Gecko will be diferent than Minotaur's one
Huh? Do you even know *anything* about how Moz/Phoenix/etc. work? Gecko is developed as a component which is embedded in applications, not as a part of applications themselves. Hence, there won't be a "Phoenix Gecko" and a "Minotaur Gecko". There will be Gecko, and Phoenix and Minotaur will embed it. From what I've read, installing them both on the same machine will likely have them share a common Gecko install, they won't even install two copies of it.
Not to mention that they want the Mail app to be able to stand alone or embed in Phoenix according to the user's wishes . . .
Re:Too risky! (Score:4, Informative)
Gecko is less messy than the old, MozillaClassic codebase. It's still messy -- it must be so, remember, because it is real. Plus, many hands have handled it. Also, it was over-designed a bit, or a lot, in places -- but that's water under the bridge.
Gecko does a *lot*, way more than the old codebase. HTML4, CSS1, CSS2.1, parts of CSS3, DOM levels 1-3, XML, XSL-T, SVG, MathML, SOAP, WSDL,
True statement: the reason we ditched the "Netscape 5" code was not because it was messy. The reason was that we simply could not interest enough new people, inside or outside of Netscape, in learning to deal with the mess, and then clean it up, and furthermore build on top of it. Almost all of the "old people" who wrote that codebase had moved on to other things.
Someone please mention this overriding non-technical fact to http://joelonsoftware.com. Joel may be right to call all the newcomers who were unwilling to work on the old codebase "undisciplined" or "unprofessional" -- if those words are fair, then all I can say is that there are not many disciplined professionals in software to be found. I worked on both codebases extensively (I created the DOM "level 0" along with JavaScript in 1995, for Nav2), but I can't claim to be either disciplined or professional.
Meanwhile, during 1998, Netscape had a team working on the "NGLayout" project, and they wanted to contribute that new layout engine. We (mozilla.org) took a chance, preferring the new frontiers of that codebase to the crowded, overdeveloped old world. The lure of the frontier, the chance to homestead your own plot, especially using XML and JS, was what mozilla.org needed most in order to attract contributors. People simply could not sink the costs required to learn the old C/C++ codebase enough to scratch their itches.
Our gamble worked, I think. Not without many bumps along the way (and whose idea was shipping Netscape 6, anyway? Not mine!). Now, our top Gecko hackers are people such as dbaron@dbaron.org, who has recently graduated from Harvard, and who is an invited expert on the W3C CSS working group; rbs@maths.uq.edu.au; and bzbarsky@mit.edu.
Yeah, it took too long. There are no shortcuts. We should have done better. But doing "just a browser" was never in the cards, and not only because of Netscape's commitments. Mozilla is and always will be more than "just a browser". As jwz wrote here a while ago, if you want just a browser, stop whining and go use Konqueror, Galeon, K-Meleon, or any of a number of choices, depending on your preferred platform. (Don't kid yourself that Mozilla could have stopped IE's distribution-channel-based takeover, no matter what we did.)
If you want to help Mozilla, please come join us. With the new roadmap, we have more new frontier land to develop.
Re:They lost me on the changes to XUL (Score:5, Informative)
Short answer: nothing; sorry we mentioned it.
Longer answer: we brought XUL up because if we "switch to Phoenix" from the app-suite browser, based on Phoenix as it has been distributed so far, we drop Mac XUL support. We don't want to do that. So in the roadmap, we go out of our way to say that we *are* going to build Phoenix for OS X, when we switch.
I wonder how we can make this simple point more clear, without inviting confusion. Jumpy roadmap readers seem to skim, and fly off the handle out of fear that we're dropping XUL, or something silly like that. Rest assured, we are supporting XUL fully.
XUL with some form-submission smarts, but using XML-RPC, SOAP, WSDL, or whatever's appropriate, should become the basis for web applications. XUL widgets should form the kernel of a pragmatic XForms implementation. And XUL's still great for cross-platform applications. We like XUL too.
Re:phoenix? (Score:3, Interesting)
Re:I really like the integrated suite.. (Score:5, Informative)
Remember, your add-ons persist across upgrades, unless an incompatible change to the new toolkit (which is XUL, XBL, JS, and CSS) invalidates a particular add-on (in which case, you'll need to get the new, compatible version of that add-on once it's out; this kind of invalidation should not happen often). So once you've added the mail extension to the browser, you're set -- you should be able to operate just as you do today with the integrated app-suite.
That's the goal, anyway, and a requirement to meet before we switch the default build.