| |||||||||||||
Lotus Symphony code for OpenOffice coming soonLotus Symphony code for OpenOffice coming soonPosted May 21, 2012 14:33 UTC (Mon) by keithcu (guest, #58738)In reply to: Lotus Symphony code for OpenOffice coming soon by chithanh Parent article: Lotus Symphony code for OpenOffice coming soon
I pointed out multiple flaws, including the fact that the same decision could be made in AOO, and the key in real life is to get enough people to figure out the right solution and have time to implement it.
You seem to think that with 2 products, you will make more users happier. You therefore don't understand the idea that people could want some of the AOO unique features and some of the LO. Unfortunately, in the real world of software, it is not possible. This is perhaps the biggest reason why comparing spaghetti to software is a bad idea. Another big reason is that the challenge with LO is not whether it needs more salt, but how are they going to get done everything they want to do. There isn't time to sit and taste the sauce. There are many reasons why I think the spaghetti sauce analogy is confusing you.
It also causes you to not recognize that you can add new features in a way to make the product more customizable. I remind you that Linux supports many file-systems. They don't bother trying to unify them, but they didn't need to make a separate team. You seem to pretend this scenario is not possible either.
Another reason it can be confusing to compare to spaghetti sauce is that people can customize LO to a massive extent already. The major point, however, is that you are arguing about spaghetti sauce because you don't have any real features. You might be able to explain the spaghetti sauce analogy very well, but you appear to be missing many more relevant facts about your own situation. I recommend becoming more curious.
"Whether the tradeoff is worth it" is actually a very big issue. Everything has tradeoffs. Do you believe considering the negative trade-offs is somehow an optional part of decision making? If you consider that your plan has lots of minuses, and that you are building a house of sand, it can also help you realize that thinking about spaghetti sauce isn't helping you.
(Log in to post comments)
Lotus Symphony code for OpenOffice coming soon Posted May 29, 2012 1:40 UTC (Tue) by chithanh (guest, #52801) [Link]
I did not say that two office suites "will" make users happier. I say that they have the potential to make users happier, which is quite a different thing. I then predicted that the divergence of AOO/LO will produce software to address different audiences.
It seems you are still struggling to understand the results from the spaghetti sauce experiment. The premise is the following: A product has certain properties that are decided by the manufacturer and not customizable by the consumer. Some consumers prefer one outcome, and others prefer another outcome.
The hypothesis is that several products, each taking the decisions to meet a different consumer preference cluster, can lead to greater total satisfaction than one product that tries to accommodate everybody.
The data gathered from the spaghetti sauce experiment, and a number of follow-up experiments, supports this hypothesis.
In particular, the following are totally inconsequential (ie. not part of the premise):
Don't forget that "customizability" itself is a decision that can attract or repel users.
That the premise applies to LO was shown by pointing to the bug about empty spreadsheet cells. That AOO can make the same decision does not invalidate the premise.
If you want to argue against applying the spaghetti sauce results to office software, you have to either say that Mr. Gladwell introduced additional premises that don't apply here, or that the spreadsheet cells behaviour is actually customizable, or that everybody prefers the same behaviour. (For the latter two cases, the counter-argument would be pointing to the next bug of that kind.)
|
|||||||||||||