Linked by Thom Holwerda on Tue 10th Feb 2009 18:31 UTC
Permalink for comment 348261
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
More News »
Sponsored Links



Member since:
2006-03-01
[...]
But I agree that it's somewhat difficult to imagine what is so extraordinary here if you never tried BeOS/Haiku before. :-)
porting existing applications like KDE ones or openoffice would require porting their base framework for the most part
the problem is, merely doing so would result in applications that would exploit little to no native feature (distinguishing ones like the translators you mentioned, in particular), would feel evidently "alien", and worse, would defy the goal (minimalism and efficiency) of the system they're ported to (due to the unnecessary layers - own framework plus "native look" skin engine - they'd retain between the app's main code and haikuOS native gui library)
in order to avoid the bloat resulting from this, differentiating (branching) the application main code, instantiating native classes instead of, say, OOo ones in platform specific code paths, would be a sensible approach from a SW design point of view
but it would effectively be the same as redesigning the application from the inside, i suspect it's unlikely it will ever be done for large applications (paradoxically often the most useful ones)
it doesnt say anything about the elegance and cohesiveness that goes in the *design* of code and in the management of a project, or the skills of people designing code, or that people tasked with porting a package will choose the best overall approach *for the target platform* (and not just for the application, or for themselves)