i have spoken perodnally with the co-developer and his team for firefox and he says that the memory issues will be dealt with by 1.5.1 or around there, appernetly the issue of memory leaks and spike is almsot 100% windows fault and is a relsut of windows code not handling some of trhe new c script and compiler options they used on FF 1.5+. anotrher example of windows lagging in code bases. it cant even render C code properly now?
LMAO
Slashdot Mirror
this is kool, good to see everyone wants to release something free, jsut keep the extra fancy stuff locked up and you can get "some" buissniess.
i have spoken perodnally with the co-developer and his team for firefox and he says that the memory issues will be dealt with by 1.5.1 or around there, appernetly the issue of memory leaks and spike is almsot 100% windows fault and is a relsut of windows code not handling some of trhe new c script and compiler options they used on FF 1.5+. anotrher example of windows lagging in code bases. it cant even render C code properly now? LMAO