Earlier quoted context omitted.
Firefox added Pocket, and kind of nobody wanted it. So it happens in FF too.
Pocket by default is one of the best feature of Firefox, for everyone. Try to use it for week.
Goodbye, EdgeHTML
461–470 of 679 posts
Re: Goodbye, EdgeHTML
#462Earlier quoted context omitted.
The best thing about Firefox is Mozilla's Multi-Account Container tabs[0]. Essentially it allows you to put different tabs into different light-weight profiles, with their own session, cookies, and state. That means if you want to log into Facebook but don't want Facebook following you online, just give Facebook its own container. Mozilla has anti-tracking already baked in, but Multi-Account Containers are a whole ot…
Totally share the love regarding container tabs. I don't, however, like how the UI/UX is implemented. In particular, the management of containers -- why do I have to dig so deeply to add new containers? Also, as a color-blind person, the slightly colored thin bar above the tab is not a sufficient identifier. It just seems all sort of after-thoughty and jumbled to me. Having said that, I converted to FF being my prima…
Re: Goodbye, EdgeHTML
#463Earlier quoted context omitted.
It's made building cross-platform desktop applications that are just wrappers for existing web-apps down-right trivial (and no web-dev experience required there.) And that case applies more often than you'd think. For example, the Spotify app, the Slack app†, the various Facebook Messenger "clients", etc. † the Slack app is built with http://macgapproject.github.io/ , but it's pretty much the same thing.
I don't understand why the slack app exists. Why would I want to run another browser for a chat application?
Re: Goodbye, EdgeHTML
#464I really wish Mozilla would work on making their Gecko engine (or whatever backend they use now) more usable to external developers. WebKit always seems very easy for developers to integrate into their apps. Whether you think it's a good or bad move, Electron has made building cross platform desktop applications a lot easier. It's a shame it must use Chromium and V8. In fairness Mozilla used to have XUL [1] until it…
Re: Goodbye, EdgeHTML
#465Earlier quoted context omitted.
How much of a rewrite was it? IIRC they fixed a lot of bloat issues and called it a rewrite, but it wasn't a full rewrite.
It wasn't much of a rewrite (at least of the underpinnings) and embedding was always fragile even when it worked. A lot of this is XPCOM overhead which can't be completely eliminated. I think the lack of embedding has hurt Gecko showing up in more projects. Their solution was XULRunner which inverts the model by embedding your app in Gecko instead of the other way around, and they don't even support that anymore. I'm…
Re: Goodbye, EdgeHTML
#466Earlier quoted context omitted.
I think Servo is going to be a massive Good Thing (tm) for Mozilla, but they have messed up a few times with UI anti-patterns and sneaking extensions into updates that users didn't opt for. They have seriously breached our trust like Google and it will take years to earn back that trust. I switched to Firefox away from Chrome recently. I am happy with this but I wish they had a friendly UI you could bring up to expos…
I'm afraid our hopes of Servo resurrecting Mozilla were short lived. From what I understand, work on Servo for Desktop has been phased out considerably. See https://blog.servo.org/2018/03/09/servo-and-mixed-reality/
Re: Goodbye, EdgeHTML
#467With Servo only just in developer preview, it's not going to be fit for Microsoft's enterprise customer needs for another couple of years, and taking a dependency on Rust would have been hard for Microsoft as it has its own languages that serve much the same purpose.
Choosing a mature browser platform written on C and C++ makes a lot of sense when thought of in those terms.
Re: Goodbye, EdgeHTML
#468Seriously, switch to Firefox. It's good again, and prioritizes privacy.[0] After Chrome's forced-sign-in debacle [1] I switched away from Chrome on all my platforms (Windows, Linux, Android) and haven't missed a thing. [0]: https://hacks.mozilla.org/2018/11/firefox-sync-privacy/ [1]: https://news.ycombinator.com/item?id=18055161
I tried switching completely a month ago for the third time.
Sadly absolutely nothing has happened in a 5 year time-span. The performance on my high-spec i7 Macbook Pro is abysmal. ( same across several company Macbooks ) The fans speed up constantly like they have done it for years. It's completely unusable for "professional" work or just regular multi tab browsing and drains the battery in no time.
Safari, Chrome, Opera, whatever, doesn't have these problems. I actually haven't experienced an application that feels so sluggish and unoptimised in OSX as Firefox. Something is seriously wrong and the dev group must not be prioritising it?
I checked their subreddit and loads of people are fleeing the Mac version, even on the newest nightly builds of quantum - seriously what the hell is going on? Why hasn't "the bug" or whatever been found or defined in clear termes in over 5 years?
The day the app works without serious CPU issues i will uninstall Chrome and go to Firefox, but the handling of this problem makes me worried about the dev groups competence.
When i talked to devs in the subreddit many of them were like "Hey, that sounds weird, should be better in the new nightly, are you sure it's not ..." - an absurd answer in the light of the constant stream of people saying this for years and years - even in this thread i see multiple people saying it's useless on OSX.
To the dev group: Get a Macbook (many devs use them), open Firefox, identify the problem - should have happened 5+ years ago.
Re: Goodbye, EdgeHTML
#469Earlier quoted context omitted.
It's made building cross-platform desktop applications that are just wrappers for existing web-apps down-right trivial (and no web-dev experience required there.) And that case applies more often than you'd think. For example, the Spotify app, the Slack app†, the various Facebook Messenger "clients", etc. † the Slack app is built with http://macgapproject.github.io/ , but it's pretty much the same thing.
I don't understand why the slack app exists. Why would I want to run another browser for a chat application?
Re: Goodbye, EdgeHTML
#470Earlier quoted context omitted.
It took away credibility. A lot of it. It also alienated too many “almost evangelist” users (like me) who had converted countless users from other browsers in high school and college. Many of them haven’t been able to reconcile with what might seem a tiny change now. Also the jarring and bizarre way Mozilla pretty much stonewalled everyone on it who wanted it to be discussed. I don’t know it would make sense to you,…
How is your experience with Pinboard?