4 ms·

It's interesting that you don't mention the absolutely unusable browser that the project is continuing to develop, instead of using a modern mature browser like

by wadera 6y ago

It's interesting that you don't mention the absolutely unusable browser that the project is continuing to develop, instead of using a modern mature browser like Chromium.

waddlesplash 6y ago
WebPositive in based on modern WebKit (specifically a snapshot from a few months ago), which is the same engine that powers Safari. Is that not a "modern, mature browser"? The bugs in Web+ are mostly in our WebKit port, which is continuing to improve. We have no interest in trying to port Chromium. Even OpenBSD, which uses X11 that Chromium already has a native backend for, has thousands of lines of patches they have to maintain (and spend hours and hours rebasing every upgrade). Haiku would have to maintain far more than a few thousand lines, as we would have to add a new graphics backend at the very least. Firefox is better in this department, but has a codebase larger than Haiku itself, and none of us have any expertise there. If someone knowledgeable about Firefox's codebase wanted to port it, we'd be happy to help where we can, but there's only so many of us.
- exikyut 6y ago
  > OpenBSD, which uses X11 that Chromium already has a native backend for, has thousands of lines of patches they have to maintain (and spend hours and hours rebasing every upgrade). Wow, you're not kidding. https://github.com/openbsd/ports/tree/master/www/chromium/patches https://github.com/openbsd/ports/tree/master/www/chromium/pa... is positively scary.
  - wadera 6y ago
    Please have a closer look at those patches. 98% of it is constituted of C preprocessor ifdefs. This means that most of them just enable the same features as Linux alongside other operating systems. Most of it is purely code configuration. Haiku instead reimplement many parts of WebKit, instead of relying on mature code. This is the reason why the WebKit performance on Haiku is so poor.
    - waddlesplash 6y ago
      You do realize that WebKit has no native graphics API, right? It uses Cairo under GTK, CoreGraphics under macOS, etc. etc. So we created a Be API implementation, and yes, it needs more optimization. But you are acting like we are reinventing the wheel here or something...
      - wadera 6y ago
        Web+ is integrated with the Haiku Network Kit and other things, accomplishing nothing for the end user. Most of the performance issues comes from there.

by wadera 6y ago

It's interesting that you don't mention the absolutely unusable browser that the project is continuing to develop, instead of using a modern mature browser like Chromium.

waddlesplash 6y ago

WebPositive in based on modern WebKit (specifically a snapshot from a few months ago), which is the same engine that powers Safari. Is that not a "modern, mature browser"? The bugs in Web+ are mostly in our WebKit port, which is continuing to improve. We have no interest in trying to port Chromium. Even OpenBSD, which uses X11 that Chromium already has a native backend for, has thousands of lines of patches they have to maintain (and spend hours and hours rebasing every upgrade). Haiku would have to maintain far more than a few thousand lines, as we would have to add a new graphics backend at the very least. Firefox is better in this department, but has a codebase larger than Haiku itself, and none of us have any expertise there. If someone knowledgeable about Firefox's codebase wanted to port it, we'd be happy to help where we can, but there's only so many of us.

exikyut 6y ago
> OpenBSD, which uses X11 that Chromium already has a native backend for, has thousands of lines of patches they have to maintain (and spend hours and hours rebasing every upgrade). Wow, you're not kidding. https://github.com/openbsd/ports/tree/master/www/chromium/patches https://github.com/openbsd/ports/tree/master/www/chromium/pa... is positively scary.
- wadera 6y ago
  Please have a closer look at those patches. 98% of it is constituted of C preprocessor ifdefs. This means that most of them just enable the same features as Linux alongside other operating systems. Most of it is purely code configuration. Haiku instead reimplement many parts of WebKit, instead of relying on mature code. This is the reason why the WebKit performance on Haiku is so poor.
  - waddlesplash 6y ago
    You do realize that WebKit has no native graphics API, right? It uses Cairo under GTK, CoreGraphics under macOS, etc. etc. So we created a Be API implementation, and yes, it needs more optimization. But you are acting like we are reinventing the wheel here or something...
    - wadera 6y ago
      Web+ is integrated with the Haiku Network Kit and other things, accomplishing nothing for the end user. Most of the performance issues comes from there.