Disruptive Technologies, or Innovator's Dilemma

I think that Mozilla.org has a super potential called Phoenix and a big problem called Phoenix too.

<hyatt> i don't hate Moz. i think Moz is a lot like Opera.
<hyatt> it's the immensely configurable web geek's wet dream.
<hyatt> but mozilla needs to produce at least one simple browser IMO
<hyatt> one simple XUL-based browser
<hyatt> i dunno. if everyting beceoms possible in phoenix via extensions, i could envision it replacing the trunk (you'd have to have a mail analog stand-alone first)
<caillon> basically, I'm curious to know if trunk UI work is in vain...
<hyatt> i've completely abandoned trunk UI work
<hyatt> i view the UI files as hopelessly entangled
<hyatt> it's too much of a mess to dea lwith IMO
<hyatt> also phoenix is independent of netscape which is nice
<hyatt> we can do what we want there
<hyatt> we're also hashing out the new toolkit for phoenix
<hyatt> then other apps can start switching over to the new toolkit
<hyatt> UI patches starve because no one knows if netscape wants it or not
<hyatt> and i can't really review things any more because i'm not in the loop
* hyatt gets back to working on his blocked images/popups reporter

Despite of what Michell Baker says, Phoenix is a disruptive technology in the world of the current Mozilla browser and disruptive technologies, that often emerge as skunk work, are allowed to progress from within the hosting organization only if they are considered as a direct future replacement for the current product.

By the way, one quoted line above contains a false assertion since one Netscape engineer works full time on Phoenix. Phoenix is therefore not independant of Netscape.