601–610 of 733 posts
Earlier quoted context omitted.
ehh I know taste is subjective, but (on Win10, at least) I find this very very ugly. latest nightly. https://i.imgur.com/z3cM8ve.jpg https://i.imgur.com/Oa875od.jpg
I find it incredibly cluttered. Seems like the push for vertical page space has lead to crunching everything together into 2 lines while ignoring usability.
Earlier quoted context omitted.
> (borrowed from MS COM) are you referring to microsoft's com (component object model)?
Yes, though more to HRESULTS from the Windows API. This meant return values could indicate success or a specific error which could be determined with macros. Rust actually has a similar mechanism in its standard lib, the Result enum whuch resembles Maybe from Haskell, but has either a returned value if successful (which can be the empty object ()) or an Error. XPCOM was modeled on the Microsoft version using the same…
Earlier quoted context omitted.
Telemetry doesn't collect any private data. It's all performance measurements. I run Nightly with all the additional opt-in telemetry flags because I want to help Firefox development.
Firefox telemetry includes a unique identifier and system information. The data Mozilla is proposing to collect includes what sites a user visits.
Honestly, (unpopular opinion probably but) I'm really tired of this privacy-mania…
EDIT: And is it possible to block third party cookies?
Boy, I _really_ didn't want to swap to Chrome. I'd held on through about a year ago, even despite knowing it was slower, a memory hog, and so on; at least this way, _someone_ on my team was viewing our site in FF and would notice discrepancies. I hated to let Google manage yet another aspect of my life. But as some point, too much was too much. Unable to bear vanilla, Google-owned Chrome, I ended up in (closed-source…
-an extension to allow to treat chrome + firefox history and open tabs as one on all devices (basically what I already have with chrome on desktop + mobile)
-a password manager that integrates with both (this one should be easy enough .. just buy lastpass or an alternative).
Earlier quoted context omitted.
While Mozilla has had quite a few projects that didn't really pan out, I'm not sure you're giving them enough credit. They developed (well... became the first and most significant major backer of) an entirely new programming language, purely for the purposes of building a better browser. And then devoted tons of resources for years into developing Servo, a massive and complex project that is only being realized now.…
> Firefox is a massive legacy codebase that couldn't be cleaned up without breaking A LOT OF THINGS, and at every step in the process they faced people begging them not to break their things, despite the alternative being the continued rot of Firefox's internals. I've made a couple small contributions to Firefox. Though I'd been a Firefox user for years, this never occurred to me until I looked at the source in 2015…
FWIW internal firefox code has had ES6-like concepts before ES6 itself; and many of these made it into the final spec in some form.
Earlier quoted context omitted.
You know that Tree Style Tabs 2.0 supports Firefox 57+ right? https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta...
I saw that - wish I could get rid of the obnoxious header though, just a frame on the left would be ideal.
Earlier quoted context omitted.
Well that, and paying every adware from here to eternity to bundle a Chrome installer...
And sticking 'Google service X is better with Chrome' on all of their sites probably didn't hurt either.
Google is not a charity, so they used their sites to advertise their own product. Microsoft is doing the same thing with Edge, even on Windows 10.
From first impressions though, I'm very impressed by how snappy it feels.
One downside is a personal site I host uses client side certs for auth, and that stopped working in Firefox (whereas it was fine in Chrome), turns out the Javascript fetch API needs you to structure the request like
`fetch(someUrl, { credentials: 'include' })`
So I had to go through the code to fix that.
Presumably this is a web standard that Firefox is adhering to, whereas Chrome is a bit more relaxed on this?
