Drawing that conclusion from Bender's departure is incorrect, Negroponte wrote: "We are scaling Sugar up, not down."
Developers replied that his vision of Sugar for Windows is muddled and that he is further dividing himself from OLPC's developer community.
"If you are not serious about Sugar on Windows within the next year, please continue to avoid 'now' and use 'might' and 'someday' when you talk about it, and we'll continue to try to make Sugar-on-Linux achieve its potential," wrote C. Scott Ananian in a community posting at the OLPC site.
"I approve of keeping OLPC's options open, in case your current development team (myself included) cannot deliver on Sugar's potential, but setting vague (and demoralizing) goals for future development -- without actually devoting the resources to achieve those goals -- is madness. You have only succeeded in alienating the developers you need to make Sugar-on-Linux work, without actually achieving any progress on Sugar-on-Windows," Ananian wrote.
Porting Sugar, which runs on multiple Linux distributions, to Windows shouldn't be hard, but the question is whether users will have the same experience on both OSes, wrote Tomeu Vizoso.
Negroponte wrote that Sugar needs to be changed from an omelet to a fried egg "with distinct yoke and white, rather than having the UI, collaborative tools, power management and radios merge into one amorphous blob."
Vizoso wouldn't chew on Negroponte's vision of a fried egg. "My understanding is that the Sugar UI is composed of inseparable components because we wanted to give an integrated and coherent experience. In which way are you suggesting to split Sugar?"