Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Goodbye, EdgeHTML

blog.mozilla.org

Post reply on HN
Print view View original

411–420 of 679 posts

Re: Goodbye, EdgeHTML

#411

Post by mixmastamyk »

esistgut wrote: post #363
davidp wrote: post #19

Seriously, 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

After quantum I did my best to switch but I had the following problems: no scrollbar search highlights, terrible Linux/gnome dark theme integration, angular source maps not working. After a couple of weeks I got back to Chrome.

Looks great on my Linux/mate dark theme. Wonder what the difference is?

Re: Goodbye, EdgeHTML

#412

Post by arsa »

turblety wrote: post #226

I 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…

They used to support it, but it was killed to prioritize firefox development (and couple of years later they stopped developing mozilla suite).

https://groups.google.com/forum/#!topic/mozilla.dev.embeddin...

otoh Webkit was originally developed as part of iOS, so embedding was required

Re: Goodbye, EdgeHTML

#413

Post by pitaj »

roywiggins wrote: post #212
untog wrote: post #29

Earlier quoted context omitted.

Look at VS Code: Electron doesn't have abysmal performance. It's just what people do with it that causes problems.

I've found VS Code to be approximately unusably slow in a virtual machine (Linux guest, Windows host) but VS Code runs fine on the host. Other editors run just fine in my Linux VMs- Sublime Text has no problem at all.

Probably a lack of hardware acceleration on the virtual machine.

Re: Goodbye, EdgeHTML

#414

Post by pitaj »

turblety wrote: post #226

I 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…

You might be interested in GeckoView [1]

[1]: https://wiki.mozilla.org/Mobile/GeckoView

Re: Goodbye, EdgeHTML

#415

Post by frankietwenty9 »

starik36 wrote: post #245
firefoxd wrote: post #222

There was a great comment i read here yesterday. Developers build stuff on chrome because the console is amazing. So if the user uses chrome, there's a guarantee the website will work. Yes, firebug started it all, but chrome is killing it right now. Mozilla, why don't you start copying the chrome console already.

What exactly is missing in Firefox DevTools? If anything, they are superior. I've switched over to Firefox DevTools for 2 reasons: 1. The box model is on the right instead of on the bottom, so I can mess with it and immediately see results in the Inspector styles window and the browser. https://i.imgur.com/KfxmRQT.png 2. I can click on the Event bubble next to the element to see events that are bound to it and go to…

Can't resize columns in 'network' tab

Step, Step Into, Resume.. use different function keys than I'm used to on Linux.

Edit + Resend doesn't work for me on Linux. It works on Windows for me.

Copying headers doesn't work well for me on Linux. I have to click 'Raw Headers' to copy a header. Works fine on Windows.

Chrome is still faster than Firefox.

I prefer chrome and Edge's download monitor.

I prefer Firefox's proxy controls.

Re: Goodbye, EdgeHTML

#416

Post by adetrest »

Switched to ff when quantum came out, never looked back. It's really fast!

And I absolutely love how the dev tools show which elements are grid and flex box containers with a little pill in the DOM explorer.

I don't see a single good reason to switch back to chrome/chromium

Re: Goodbye, EdgeHTML

#417

Post by vtesucks »

I don't want to digress from the discussion but can a typographical expert comment on what are the legibility benefits of wide vs slender fonts? How much or how little does the width matter? What other factors are there?

I ask because the "goodbye" headline uses a wide font.

Re: Goodbye, EdgeHTML

#418

Post by baroffoos »

derefr wrote: post #364
PunchTornado wrote: post #103

Earlier quoted context omitted.

as a frontender I'm not sad. A lot of bugs coming in from Edge. And Edge has a pretty shit debugger too. So no tears for me. Waiting for Safari to die. Firefox and Chrome are good.

Why would Safari [i.e. Webkit] die? Looking at desktop + mobile market shares, if anyone would be "the next to die", it'd be Firefox.

Safari is a huge pain in the ass to test on because you have to own apple hardware to do it. Firefox and chrome can be installed on anything and microsoft gave you a VM to test IE and Edge in.

Re: Goodbye, EdgeHTML

#419

Post by npunt »

pseudalopex wrote: post #377
npunt wrote: post #343

Earlier quoted context omitted.

Purely from a feature development perspective, I guess I don't see how adding a read-it-later / bookmarking feature would generate so much consternation. Functionally its roughly equivalent to Reading List + Bookmarks on Safari, with some delicious-like aggregate smarts. Would it have been better to have built it internally instead of through acquisition? I admit I'm unfamiliar with the inside baseball on it's integr…

Mozilla was developing a private Reading List feature that used Firefox Sync. They suddenly replaced it with Pocket, which sent users' bookmarks to a third party that engaged in data mining. (The acquisition came later.) Users suspected money was involved. Mozilla employees insisted that Pocket hadn't paid for the integration. Months later, it came out that there was a referral deal. Pocket was and is an extension. I…

Thanks for the details. Sounds like it wasn't handled well.

Re: Goodbye, EdgeHTML

#420

Post by baroffoos »

tflinton wrote: post #177
nightski wrote: post #4

It makes me wonder if at any point in the process Microsoft approached Firefox over integrating their rendering engine vs. Chromium and if so, what the factors were in making their final decision. I also wonder if instead of "ceding" control to Google, Microsoft intends to start being a major contributor to Chromium, so much so that it almost becomes a joint effort vs. Google dominance.

Firefox is also undergoing a large rewrite with the quantum stuff with more of an emphasis on rust. Chromium is c++ and already has decent tooling for embedding. Honestly, Firefox is trying to be where the puck is going. Chromium is great but stagnating.

What do you mean by chromium is stagnating?
Post reply on HN