Otter Browser – Aims to recreate the best aspects of classic Opera UI using Qt5 - https://news.ycombinator.com/item?id=18830430 - Jan 2019 (47 comments)
Opera 12.15 source code - https://news.ycombinator.com/item?id=13417307 - Jan 2017 (86 comments)
11–20 of 98 posts
Otter Browser – Aims to recreate the best aspects of classic Opera UI using Qt5 - https://news.ycombinator.com/item?id=18830430 - Jan 2019 (47 comments)
Opera 12.15 source code - https://news.ycombinator.com/item?id=13417307 - Jan 2017 (86 comments)
Earlier quoted context omitted.
> chromium Are there any Google risks for being chromium-based? Honest question here.
As noted in a sibling to your comment, there's a choice between WebKit and Blink (your build allowing). Here's QT's note addressing your concern in QtWebEngine: https://wiki.qt.io/QtWebEngine#Relationship_to_Chromium Auxiliary services that talk to Google platforms are stripped out
I'm not well versed enough in the Browser Wars to say one thing or another about except this: I like the name. It lends it self to saying "I use the Otter browser" which is not just a great pun but the pun on 'other' defines what Otter is, the "other" browser. The web needs independent browsers. We need to get rid of the idea that websites are designed to work on any one technology. They should work on any browser th…
> The web needs independent browsers...[websites] should work on any browser Unfortunately, independence ends with the choice between WebKit (QtWebKit) or Blink (QtWebEngine), albeit with a faithful Opera 12-like interface that's less resource hungry than Vivaldi. Otter is still in development and it shows in some rough spots and occasional crashes.
This seems actually viable. And those weekly updates let us know "It's Alive!!" not some zombie. I'm going to make an effort on using this. I'm currently using a Firefox fork but the maintenance is a little rough and I get conflicts with upstream sometimes that are hard (for me) to resolve.
They do not fix it for years now which for me means one thing: they do not understand how basic this functionality is and if so I think this 'mainstream' has lost it's sight.
For me as long as such idiocy exists in 'mainstream' I consider it doomed. Because if you do not fix such basic things the next question is: what else you did not fix ..
Another idiocy is that they push updates through your throat without option to stop checking for it or stopping dialog asking to update. It always appears when you do not want it to appear and breaks the flow of your work. I consider it a disrespect to a person who uses it. And again in my opinion as long as it exists I think it's doomed.
Earlier quoted context omitted.
> chromium Are there any Google risks for being chromium-based? Honest question here.
I can't find a source, but I know Brave has had upstream Google issues in the past. Unfortunately, from what I've heard, Gecko is not very developer friendly, so Google is pretty much the only option.
I'm not well versed enough in the Browser Wars to say one thing or another about except this: I like the name. It lends it self to saying "I use the Otter browser" which is not just a great pun but the pun on 'other' defines what Otter is, the "other" browser. The web needs independent browsers. We need to get rid of the idea that websites are designed to work on any one technology. They should work on any browser th…
> The web needs independent browsers...[websites] should work on any browser Unfortunately, independence ends with the choice between WebKit (QtWebKit) or Blink (QtWebEngine), albeit with a faithful Opera 12-like interface that's less resource hungry than Vivaldi. Otter is still in development and it shows in some rough spots and occasional crashes.
Earlier quoted context omitted.
> The web needs independent browsers...[websites] should work on any browser Unfortunately, independence ends with the choice between WebKit (QtWebKit) or Blink (QtWebEngine), albeit with a faithful Opera 12-like interface that's less resource hungry than Vivaldi. Otter is still in development and it shows in some rough spots and occasional crashes.
I'd love to go back to 1999 and see everyone's reaction when I tell them that almost everyone in the 2020s uses a browser derived from Konqueror, and that you have your choice of Konqueror derivatives from Apple, Google, or Microsoft. Whoever named it was more prescient than they realized.
$ brew install otter-browser
What's also interesting, is that the tab-close button is on the left of the tab, like every other macOS application. Other browsers (Chrome, Firefox) put it stubbornly on the right.