Goodbye, EdgeHTML • Hacker News Board

Re: Goodbye, EdgeHTML

#211

Post by dredmorbius » Thu, Dec 06, 2018, 10:53 PM UTC

tptacek wrote: post #125

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

Does it prioritize privacy? I haven't used Firefox in a long time, so my impressions of it are based on news stories, like them launching a partnership with sketchy VPN services or building in "easter egg" advertisements for television shows.

Sgnificantly more than Chrome, yes.

Not sure relative to Safar or Edge.

Re: Goodbye, EdgeHTML

#212

Post by roywiggins » Thu, Dec 06, 2018, 10:54 PM UTC

untog wrote: post #29

cududa wrote: post #23

Earlier quoted context omitted.

Everyone seems to be missing that this is Microsoft’s tacit recognition that Electron is the future of apps. Electron has abysmal performance and doesn’t work on ARM. This is them fixing fundamental chromium issues, to improve Electron performance and give themselves a further wedge beyond TypeScript

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.

Re: Goodbye, EdgeHTML

#213

Post by 21 » Thu, Dec 06, 2018, 10:55 PM UTC

pickpuck wrote: post #198

Which is better: 1 specification in psuedocode that 4 companies implement unevenly, or 1 codebase that 4 companies contribute to?

What is better? Having GCC/Clang/MSVC or having a single C/C++ compiler people/companies contribute to?

Re: Goodbye, EdgeHTML

#214

Post by [deleted] » Thu, Dec 06, 2018, 10:56 PM UTC

untog wrote: post #29

cududa wrote: post #23

Earlier quoted context omitted.

Everyone seems to be missing that this is Microsoft’s tacit recognition that Electron is the future of apps. Electron has abysmal performance and doesn’t work on ARM. This is them fixing fundamental chromium issues, to improve Electron performance and give themselves a further wedge beyond TypeScript

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

[deleted]

Re: Goodbye, EdgeHTML

#215

Post by DonHopkins » Thu, Dec 06, 2018, 10:56 PM UTC

dman wrote: post #135

scrollaway wrote: post #83

Earlier quoted context omitted.

Dropping XUL was necessary and if anything, should have been done earlier. I disagree they didn't "have a credible alternative lined up". Are you upset over extensions breaking? There was a long , extremely long deprecation period and afaik Mozilla helped addon authors move over. They had to make the cut at some point, tbh.

I wrote some extensions myself over the years, all my time writing those extensions went down the drain.

All my time writing Internet Explorer extensions and HTA desktop apps in C++ and JavaScript and HTML with ActiveX went down the drain, but those skills got me a job writing xulrunner desktop apps in C++ and JavaScript and XUL with XP/COM. And then all that work went down the drain too!

Now I know how to write Electron apps, but before you know it, all that work is going to go down the drain, too! Get used to it. ;)

Change is good, and each iteration gets better, and if you're not enthusiastic about learning new stuff all the time, you're in the wrong industry. I do NOT want to go back to ActiveX or XP/COM, thank you.

Did you know that Mozilla actually invented words to describe the process of removing XP/COM: "DeCOMification" and "DeCOMtamination"?

https://news.ycombinator.com/item?id=12968830

Re: Goodbye, EdgeHTML

#216

Post by lostmsu » Thu, Dec 06, 2018, 10:57 PM UTC

untog wrote: post #29

cududa wrote: post #23

Earlier quoted context omitted.

Everyone seems to be missing that this is Microsoft’s tacit recognition that Electron is the future of apps. Electron has abysmal performance and doesn’t work on ARM. This is them fixing fundamental chromium issues, to improve Electron performance and give themselves a further wedge beyond TypeScript

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

It might well be true for an IDE, which has a ton of features on its own, and 200MB+ Electron adds to it barely matter. But when that happens to your IM, plain text editor, music player, it adds up.

Re: Goodbye, EdgeHTML

#217

Post by BoumTAC » Thu, Dec 06, 2018, 10:57 PM UTC

Honestly I want to move to firefox but there is still so many things wrong. It's a lot better but after trying to migrate for 30min I already find 2 basic missing features from chrome.

The first one is the tab research feature. It available for many years in chrome I don't understand why it's still missing in firefox. I can't type "yo [hit tab] my video" to find a video on youtube.

And the second feature missing is the search highlight in the scrollbar. It's a mandatory feature for my when searching on a long page (like this one for example) to search for "firefox" and find in the scrollbar everywhere it is. It's a feature available in chrome for the beginning I think.

Re: Goodbye, EdgeHTML

#218

Post by Amezarak » Thu, Dec 06, 2018, 10:58 PM UTC

untog wrote: post #29

cududa wrote: post #23

Earlier quoted context omitted.

Everyone seems to be missing that this is Microsoft’s tacit recognition that Electron is the future of apps. Electron has abysmal performance and doesn’t work on ARM. This is them fixing fundamental chromium issues, to improve Electron performance and give themselves a further wedge beyond TypeScript

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

In my experience electron apps, including VS Code, have atrocious performance on older hardware where native apps like Visual Studio run great.

By atrocious performance, I mean even such things as the application significantly lagging behind my typing speed.

At any rate, I’ve often wondered when the endless pile of layers and abstractions has to topple.

Re: Goodbye, EdgeHTML

#219

Post by eightysixfour » Thu, Dec 06, 2018, 10:59 PM UTC

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

Except for the battery life on laptops. Edge and Chrime are way ahead here and it is very frustrating.

Re: Goodbye, EdgeHTML

#220

Post by shmerl » Thu, Dec 06, 2018, 10:59 PM UTC

Well, MS could choose Gecko/Servo, to balance things out. Kind of surprising they didn't. At the same time it's probably good. Having MS influencing Gecko/Servo doesn't sound like a good idea.