If I were building a new browser, priority 0 would be uBlock Origin support with a front-page guarantee it will never be neutered by any future "standards".
Otter Browser
81–90 of 98 posts
Re: Otter Browser
#82Re: Otter Browser
#83Earlier quoted context omitted.
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…
> ...its weapon of monopoly is effectively change... Rather novel weapon. This won't work, rapid change will just leave the large base of web developers behind. Tutorials and practices based on the Old Way hang around for decades. Google putting out a standard is only going to help them if it is (a) in demand by web devs and (b) competitive with the old way of doing things. I don't particularly like web apps, but the…
Chrome started forcing tab grouping on mobile so I've tried switching to Firefox. My bank's log in screen doesn't work and posting to Facebook Marketplace is broken. Not sure why basic functionality like that doesn't work but it does force me to keep Chrome around.
Re: Otter Browser
#84Earlier quoted context omitted.
Do you like the name better than "Chrome"? If someone says "I use Chrome" what does than mean to you? Just curious. Perhaps some websites do not make use of all the standards, thus browsers do not need support for all the standards for these websites to "work". For example, HN does not require a popular browser. In fact it can even be used without a browser. Why are so many "web devs" using HN but few to none of them…
Web devs make the websites they are paid to make. I'm not sure why you think their output would reflect their taste rather than their employer's taste.
Exactly! In a lot of areas, we hear talk of how "the developers"[0] made this decision or that decision (e.g. mobile apps, games, web).
But in reality, most developers have very little agency over technical decisions. Sure, they're the ones actually building it and choosing the exact tools and frameworks, but they have almost 0 control of their own constraints.
Metaphorically, companies decide they only want to use nails because they're cheaper. Even if screws would be better. The conversation inevitably turns into frustration with developers' overuse of hammers.
[0]: I get that we say "developers" to also include publishers/etc, but the term often morphs back into blaming the "technical implementers" on the team.
Re: Otter Browser
#85I'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…
It lends itself running on a mobile phone with an OtterBox case.
Re: Otter Browser
#86If I were building a new browser, priority 0 would be uBlock Origin support with a front-page guarantee it will never be neutered by any future "standards".
Shoot. Has uBlock Origin been neutered in Firefox?
I've been using it since the beginning and never bothered to check whether or not support has been reduced in some form.
Re: Otter Browser
#87If I were building a new browser, priority 0 would be uBlock Origin support with a front-page guarantee it will never be neutered by any future "standards".
Shoot. Has uBlock Origin been neutered in Firefox? I've been using it since the beginning and never bothered to check whether or not support has been reduced in some form.
No, not yet, and hopefully never, but they're not flat out promising it.
Re: Otter Browser
#88I'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…
> [..] it is churning the standards so much that its weapon of monopoly is effectively change --- Firefox can barely keep up, and Microsoft already surrendered.
Re: Otter Browser
#89[deleted]
Re: Otter Browser
#90Earlier quoted context omitted.
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.
I do too, but what I miss is customized throttling settings (I need to optimize for fast overseas connections: high bandwidth but also high latency). Chrome (and Edge) have this.
Firefox has this too. You can do it the network tab[1] or in the Responsive Design Mode[2]. There's drop downs there where you can control how much you want to throttle
[1] https://developer.mozilla.org/en-US/docs/Tools/Network_Monit...'
[1] https://developer.mozilla.org/en-US/docs/Tools/Responsive_De...