![]() It just isn’t You know you’ll never get OW into the App Store using private APIs (note: this is a joke, OK? I know Ken is well versed with App Store guidelines). I’m really struggling to recreate my OW-based environment in another browser. I’d be willing to pay again for the privilege of having the pleasure of using OW. I paid for OW (first at MacWorld NYC) and purchased new & upgrade licenses since. I think nailed it: “A world without OmniWeb is a significantly less productive and less enjoyable…”. (As I have for the last 25 years: 1994 - 2019.) But I’m afraid it’s not in a place where I’d recommend anyone else use it right now. I’m not quite ready to write OmniWeb off as a lost cause, especially since I still use it as my primary desktop browser. But that sort of migration seems likely to be a fairly big project, and I have a limited amount of spare time to work on it. Those engines seem to have all the public API needed to actually build a useful browser, which would certainly be an improvement. I’d love to get this back to a state where I’d feel comfortable putting out new public builds again, so I’ve been contemplating building on top of other engines-possibly the Firefox engine, but most likely the Chromium engine. (The only way I’ve been able to get OmniWeb working as well as I have on top of WebKit 2 is through the use of a bunch of private API, which makes me uncomfortable.) WebKit 2 does have some great improvements (and is better supported), but it’s missing public API for features I consider critical in a web browser, such as autofilling passwords. I’m writing this from an internal build of OmniWeb that is built on top of WebKit 2 instead, and it’s stable and fast and renders well… but I’m not sure it’s a viable long-term direction. (Apple has been warning developers to get away from WebKit 1 for a while, so this isn’t exactly a surprise.) The problem here seems to be that WebKit 1 is deprecated and is no longer working very well. I know that then commits OG to providing support, but I think there’s enough fans out there who would pay (like I’ve done numerous times) for a solid alternative to the “free” browsers out there that are invasive. Honestly, I’d be more than happy to pay for OW. I’ve trashed the OW6 Container (after backing it up, of course) thinking something in there was causing me problems, but that hasn’t helped. Is there something I can do on my end to fix this? 12:12:36.002 EDT OmniWeb: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set set a breakpoint on _dispatch_bug_deprecated to debug I see this error from the Console in the Crash Catcher window: ![]() I just updated yesterday to 10.14.4 and since then OW is so unstable that I’m going browser shopping as I need second browser (in addition to Safari) to keep personal and other stuff operate. I’m running the latest public build of OW 6 (as noted in the subject) and it’s crashing on 10.14.4 to the point of being unusable.
0 Comments
Leave a Reply. |