"Mandrake is the ONLY good thing ever to come from France. I assume from this statement that you don't drink wine, and don't eat at all."
I would hope this was meant in gest. If not, I would encourage the writer to keep in mind that many of the principles embraced by Jefferson and others in the Declaration of Independence and the Constitution of the U.S. were based on the ideas of Voltaire and Rousseau. Or, I would encourage the author to read some Anatole France, Zola, Camus, or Dumas, or really take in the beauty of a Cezanne, Renoir, Monet, or Matiesse, and perhaps listen to Ravel, Couperien, or Debussy. Even sampling a small amount of these other creations of France by a Mandrake user would be appreciated.
Greetings;
As one of the previous threads mentioned, Jon Lasser's _Think Unix_ (Que: ISBM 0-7897-2376-X) should be one of your first purchases. Rather than just taking the approach of showing you how to use commands, it presents the concepts behind how to use Linux/Unix, including some later chapters dealing soley with X.
And, to become more comofortable with the power and flexibility of one of Linux/Unix's many shells, you may want to look at running the Cygwin port of the GNU utitlites for Win32: http://www.cygwin.com
OK, it could be that my reading comprehension is well below what it should be, but Suck really didn't offer a reasonable explanation as to why Mozilla failed, even though it was obvious; Mozilla has had problems because there was no focus or direction for the whole project effort. What was the Mozilla project's goal? Was that goal or target measureable in an objective way?
IMHO, I think this is why it "failed", not because of feature bloat. Feature bloat is just a symptom of a major problem in correctly managing a software development project. Skins, yet another IM package can be viewed as bloat; integrated XML parser, valuable tool, if not essential or required element in this day and age. Yes, "late, fat and ugly" is no way to release any code, even if it's Open Source, but I think a bit more thought on the why from Greg Knauss would have been better.
And it would have been even more interesting reading fodder if this problem of having simple but effective project development management practices in place was placed in the context of Netscape having had, and still having problems in delivering, and how this can and does impact Open Source development efforts.
I have no problem with Knauss's opnion, just I think he missed the point, and a great opportunity to apply it to what had happend and how it can impact Open Source. If Mozilla really is dead, make sure the death wasn't in vain, draw some lessons learned from it instead of lighting a match in a gas filled room...
Slashdot Mirror
"Mandrake is the ONLY good thing ever to come from France. I assume from this statement that you don't drink wine, and don't eat at all."
I would hope this was meant in gest. If not, I would encourage the writer to keep in mind that many of the principles embraced by Jefferson and others in the Declaration of Independence and the Constitution of the U.S. were based on the ideas of Voltaire and Rousseau. Or, I would encourage the author to read some Anatole France, Zola, Camus, or Dumas, or really take in the beauty of a Cezanne, Renoir, Monet, or Matiesse, and perhaps listen to Ravel, Couperien, or Debussy. Even sampling a small amount of these other creations of France by a Mandrake user would be appreciated.
Greetings; As one of the previous threads mentioned, Jon Lasser's _Think Unix_ (Que: ISBM 0-7897-2376-X) should be one of your first purchases. Rather than just taking the approach of showing you how to use commands, it presents the concepts behind how to use Linux/Unix, including some later chapters dealing soley with X. And, to become more comofortable with the power and flexibility of one of Linux/Unix's many shells, you may want to look at running the Cygwin port of the GNU utitlites for Win32: http://www.cygwin.com
OK, it could be that my reading comprehension is well below what it should be, but Suck really didn't offer a reasonable explanation as to why Mozilla failed, even though it was obvious; Mozilla has had problems because there was no focus or direction for the whole project effort. What was the Mozilla project's goal? Was that goal or target measureable in an objective way?
IMHO, I think this is why it "failed", not because of feature bloat. Feature bloat is just a symptom of a major problem in correctly managing a software development project. Skins, yet another IM package can be viewed as bloat; integrated XML parser, valuable tool, if not essential or required element in this day and age. Yes, "late, fat and ugly" is no way to release any code, even if it's Open Source, but I think a bit more thought on the why from Greg Knauss would have been better.
And it would have been even more interesting reading fodder if this problem of having simple but effective project development management practices in place was placed in the context of Netscape having had, and still having problems in delivering, and how this can and does impact Open Source development efforts.
I have no problem with Knauss's opnion, just I think he missed the point, and a great opportunity to apply it to what had happend and how it can impact Open Source. If Mozilla really is dead, make sure the death wasn't in vain, draw some lessons learned from it instead of lighting a match in a gas filled room...