[haiku-development] Re: R1/a4 initial planning



Hi,

Am 28.02.2012 16:54, schrieb PHilip RUshik:
> Its true that shared libraries are stored and loaded once, but that 25mb
> of code still need to be processed by the processor for it to do
> anything, and that isn't just going to happen once. Shared libraries
> help with hard disk space and memory usage, but not speed, which is my
> main concern, in which case 25 mb is quite heavy, that is how you should
> look at it IMHO.

Well, on one hand there is your personal experience of Qt appearing to 
be slow in that project you encountered it in. I can't really say 
anything about that, as there are so many possible reasons for your 
experience. 


There's only one way to determine if Qt is slower than the current Haiku/BeOS 
API, that is to build
a comparison application that does very similar functions to a native 
application. Then do an 'apples 
to apples' comparison. In this way you could objectively compare code size, 
loading time, execution time,
response time, and any other observable affects. Natively integrating Qt would 
of course make things
faster but you would have some starting numbers to look at before committing a 
lot of development time.
It would be a good idea to perform a 'pilot' development project like this 
before making any decisions to
integrate Qt into Haiku. 


Planning isn't as exciting as coding but it certainly can save you a lot of 
uncoding.


Regards,
Andrew

Other related posts: