I find this thread rather annoying as people are just making a wishlist, and no progress is made. To me as the main Web+ maintainer, this is not so nice, because I put a lot of work on the browser, and I don’t get a single “thank you for your hard work”. Only complaints that it’s a crashy mess (and indeed, it is). But I also get no help. I had to wait for a GSoC candidate and another new developer who have finally started to peek into the code and fix bugs. I cannot thank the community here.
On the technical side, WebPositive is using WebKit, which means it has potential to be as good as Safari and any browser that runs on iPhone and iPad. So we’re building on a solid and well maintained base, and, more importantly, we have something working right now, and good integration with the OS. This is in line with my vision of how Haiku should be. You can disagree, but if that’s the case, you should not complain about my work, you should head over to haikuports and start writing recipes for Chrome and its dependencies. And if you can’t do that, I don’t think you can have an enlightened advice on which technical choices are better. Extrowerk was a bit agressive in tone, but made a good summary of the challenges in bringing Chrome or Firefox to Haiku. They are not all that much different from the work on WebKit.
We also have positive support from the WebKit team, if the new contributors to the codebase stay around after the summer it means we will have a team large enough to sustain both keeping the browser up to date, and finally starting again to upstream our changes to the main WebKit repo, lowering the maintenance efforts. And now that we are finally at this point, everyone complains that we should drop years of effort and start the process over with another browser?