3 ms·
> So, now you just need to build a highly-optimizing, C++ compiler instead of a browser? No. You just use gcc. Like everyone else.
by ori_b 10y ago
> So, now you just need to build a highly-optimizing, C++ compiler instead of a browser?
No. You just use gcc. Like everyone else.
- nickpsecurity 10y agoThe gist of the comment was whether GCC automatically made something like WebKit + JIT + Native Client work on very, different OS by a simple compile. I doubted that was true or that the work was easy.
- ori_b 10y agoYou only need to implement the window system and widget rendering glue. The layout, javascript, CSS, DOM, history, etc is all platform independent. But implementing `drawButton()`, `blitToScreen()` and similar is in no way similar to implementing a C++ compiler, as you implied. An example of a port is here, in this directory: https://trac.webkit.org/browser/trunk/Source/WebCore/platform/efl https://trac.webkit.org/browser/trunk/Source/WebCore/platfor...
- nickpsecurity 10y agoSounds a lot better than I thought. Appreciate the explanation. :)
- kobeya 10y agoI ran firefox on BeOS.
- nickpsecurity 10y agoIm curious how it ran. Was there a performance boost from BeOS architecture?
- kobeya 10y agoNot noticeably. It just rendered better than the built in browser..
- jwatte 10y agoI prefer clang.