Otter Browser

Post by molasses » Thu, Jul 01, 2021, 8:58 AM UTC

molasses wrote: post #48

Logo could do with a makeover. Possibility of a really nice cute graphic. Firefox seem to have repeatedly missed that opportunity. And the O is a bit reminiscent of Opera. ( I read it hopes to ape some of the better bits of Opera's past.) Certainly space for an innovative - I'm in the driving seat type browser. The space is really lack-lustre, and not in a good way.

Post by tarsinge » Thu, Jul 01, 2021, 9:28 AM UTC

userbinator wrote: post #22

geocrasher wrote: post #6

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…

They should work on any browser that supports the standards. 10-15 years ago I would agree, but now I feel I must add something to that sentence: any browser that supports the standards before they became Google-ified because it is churning the standards so much that its weapon of monopoly is effectively change --- Firefox can barely keep up, and Microsoft already surrendered. What we really need to get rid of is the…

Post by mariusor » Thu, Jul 01, 2021, 9:49 AM UTC

jordemort wrote: post #17

ibraheemdev wrote: post #10

Earlier quoted context omitted.

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 feel like Mozilla's decision not to prioritize support for embedding Gecko ended up being a strategic error in the long-term. Other browsers using Blink don't add directly to Chrome's market share but having it embedded everywhere means that its quirks don't end up being perceived as Chrome-specific. If five different browsers all behave the same way and the sixth one differs, then the sixth one ends up looking lik…

Post by zelphirkalt » Thu, Jul 01, 2021, 10:15 AM UTC

BiteCode_dev wrote: post #40

dleslie wrote: post #29

Earlier quoted context omitted.

And, let's be clear, Google's ability to enact change is a result of their pervasive influence over the internet. It took _years_ for XMLHTTPRequest to become a dominant influence on site design. Google can push new standard changes in fraction of the time because _their services demand it_. > Even webapps, which are more sensitive to browser environments due to their heavy use of JS, should not stop working on an ol…

Well, it's not like the entire web community haven't warned about it for the last 10 years. At this point, what can we do?

Post by berkes » Thu, Jul 01, 2021, 10:23 AM UTC

the_other wrote: post #56

tarsinge wrote: post #53

Earlier quoted context omitted.

It will not change until dev stop developing on Chrome as their main browser. Maybe tooling could be an excuse for very large webapps, but otherwise and especially for websites (hello simple forms broken except if you use Chrome) it's definitely not. Also it's orthogonal with JS usage, anecdotically I mainly work on JS heavy websites and don't use Chrome.

I dev in Firefox. It’s great! The tooling’s really good. It’s subtly different from Chrome and you’ll feel a twinge of friction moving, but by and large, it’s easy. Just shut it down and restart it every couple of days because it’s memory usage isn’t as tight.