Linked by Eugenia Loli-Queru on Wed 5th Apr 2006 01:06 UTC
The One Laptop Per Child organization will use Linux on its inexpensive machines, but the operating system suffers the same code bloat as Windows, the project's leader said Tuesday. My Take: A few months ago I blogged about this as if I knew what was coming. I still believe that the $100-laptop project should be targetted as an embedded application and so Qtopia with ARM is a better/cheaper/faster solution than Fedora/RHEL with x86. If Palm is able to sell the Zire 22 at $99 and still make lots of profit (yes, they do), then it is probably feasible to manufacture and market my suggestion at $100.
Thread beginning with comment 111747
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-06
KDE has the stability, feature-set, and resource usage to show that Qt/C++ was a good pick. Consider how easy it was for KDE to change their file-selector in comparison to the six months's work it took Gnome to change theirs, or the problems Gnome had until last year with applications not respecting the global toolbar preferences entered by the user.
The problem with KOffice is that it has a tiny number of developers and a large and very old code-base.
Qt4 offers a lot more to developers, which reduces the work that individual developers need to do, making them more productive. Thus, when KOffice is re-written in Qt4, they will be able to ditch a lot of custom and old code for the well tested (tested by every other KDE developer!) features offered by Qt. While this could be characterised as a port, the depth and extent of the changes being made means that "rewrite" is a better term for what they have set out to do.
Lsstly, rewrite doesn't necessarily imply more errors. While errors will occur, the prior knowledge generally serves to help developers avoid a lot of the semantic errors that had to be tweaks in the previous version. Further, that prior knowledge allows developers to write cleaner code, which again helps reduce the amount of semantic bugs.