Serious Discussion Quick Play with McAfee

[Miraculix]

For what its worth & I do understand that other members do have popups which I would find very annoying, I have yet to have a single popup & that's since last July, I have used Kaspersky as well (not together) & yes is you like buttons to twiddle there are none on McAfee & for me that makes no difference, the point for me is do you really need them?? I just looked & from cold the UI took 4 seconds to load from a boot & IMHO its pretty much perfect AV, no huge logging telling you of each & every irreverent event, it does does the job - I'm actually a person that likes my install to look good but in McAfee's case I'm really willing to put up with it, I still have 522 days left on a pittance of a payment & its on several others PC's with no apparent issues from anyone

I have to admit that I've relapsed and reinstalled McAfee. Apart from the pop-ups, it's simply a perfect antivirus.

 

[Sunqfu]

 

[piquiteco]

Virus detected Blocked by McAfee.

Spoiler: Virus detected Blocked by McAfee

 

[Jonny Quest]

The slow loading of the GUI is for me the reason not to use McAfee anymore. I can not stand when i want to open a GUI and have to wait.
I know can press the home icon, but thats not the solution for me.

Around 4 - 5 seconds here, instant after that? not sure why

It was the same issue for me with McAfee. F-Secure on this laptop (HP laptop was a bit more responsive) was 3-5 seconds to load the UI, now with ESET on this same laptop, 1 second. Maybe it has to do with F-Secure using WebView2, and ESET using C++, which on this laptop was a very noticeable difference. A stripped down summary by Gemini Plus.

Why this explains the 3–5 Second Delay
Even though everything is loading instantly off your fast SSD, spinning up a modern browser framework takes significant computational effort:

The app has to initialize the .NET runtime environment.

It has to spin up the Chromium (WebView2) rendering processes.

It has to compile the local JavaScript files to figure out where the buttons go.

The Contrast with Native Apps (Like ESET)

In contrast, ESET is written in native C++. It doesn't use an embedded browser engine. When you open ESET, it talks directly to the Windows operating system's built-in graphical engine to draw standard windows and buttons.

 

[Trident]

It was the same issue for me with McAfee. F-Secure on this laptop (HP laptop was a bit more responsive) was 3-5 seconds to load the UI, now with ESET on this same laptop, 1 second. Maybe it has to due with F-Secure using WebView2, and ESET using C++, which on this laptop was a very noticeable difference. A stripped down summary by Gemini Plus.

Why this explains the 3–5 Second Delay
Even though everything is loading instantly off your fast SSD, spinning up a modern browser framework takes significant computational effort:

The app has to initialize the .NET runtime environment.

It has to spin up the Chromium (WebView2) rendering processes.

It has to compile the local JavaScript files to figure out where the buttons go.

The Contrast with Native Apps (Like ESET)

In contrast, ESET is written in native C++. It doesn't use an embedded browser engine. When you open ESET, it talks directly to the Windows operating system's built-in graphical engine to draw standard windows and buttons.

It's a bit more nuanced than just using local, precompiled C++ vs using WebView. Precompiled C++ defaults to software-based rasterizer and opens a bunch of risks which I will not discuss in details.

It's all about how much effort and thought you are willing to put. There are plenty of native UIs that feel slow, sluggish and inferior.

Arguably, the .Net Framework adds a huge overhead (way more bigger than WebView) to F-Secure and McAfee uses a massive framework called Angular.

Some of us have mastered WebView, McAfee and F-Secure did not.



vs pre-compiled

 

[Szellem]

It was the same issue for me with McAfee. F-Secure on this laptop (HP laptop was a bit more responsive) was 3-5 seconds to load the UI, now with ESET on this same laptop, 1 second. Maybe it has to due with F-Secure using WebView2, and ESET using C++, which on this laptop was a very noticeable difference. A stripped down summary by Gemini Plus.

Why this explains the 3–5 Second Delay
Even though everything is loading instantly off your fast SSD, spinning up a modern browser framework takes significant computational effort:

The app has to initialize the .NET runtime environment.

It has to spin up the Chromium (WebView2) rendering processes.

It has to compile the local JavaScript files to figure out where the buttons go.

The Contrast with Native Apps (Like ESET)

In contrast, ESET is written in native C++. It doesn't use an embedded browser engine. When you open ESET, it talks directly to the Windows operating system's built-in graphical engine to draw standard windows and buttons.

It’s not just when the user interface takes a long time to open that bothers me—it’s also when the antivirus software slows things down. Often, you don’t notice this until, for example, there’s a heavy load on the processor or hard drive. I ran into this yesterday. I copied a large file from the SSD to the hard drive, then opened a portable hard drive—or rather, connected it—and the system slowed down so much that I thought I was going to lose my mind.

 

[Sunqfu]

Version 1.39.160.1 released.

 

[jtshadow92]

I do wish they would release a changelog like other security providers. I get a popup once in a while but its not consistent

 

[Trident]

I do wish they would release a changelog like other security providers. I get a popup once in a while but its not consistent

Yeah, the popup is generally for new features but majority of changes are in the engines.