Hacker News new | ask | show | jobs
by rntksi 1544 days ago
We've been running ESET Nod32 for over a decade.

Its strength is that it uses very low memory and CPU cycles due to the way it is built.

It ticks all the boxes you've given above.

1 comments

I've considered Eset a few times before. Never went all the way yet. Thank you.

Anything in particular you want to add about it that might be a good tip or so? Something that only someone who's been using it for a while will know, kind of thing.

Back in 200x, we had a very old machine. It had 64Mb of RAM only. We had to install AV on this and through sifting through the AV softwares, only eset nod32 ran on it without slowing it down or taking too much resources. I like how they optimised it to the point where I could run it on that old machine. They say they write it in Assembly but I think it's just a marketing ploy. However the result satisfies me enough.

From then until now our business has gone through a lot but ESET has never been something that bothered us too much. It just sits in the background doing its thing. I have terrible memories of Symantec / McAfee just being annoying, but Nod32 is just the thing you install, it sits there and you can forget about it.

Ah yes. Assembly. I really should get around to learning it so I can test some game designs on my model 1 sega genesis.

I don't know if it's a marketing ploy rntksi. What you are describing so far sounds very much like it has been written in something like Assembly if not actually assembly. From what I know at least. (Could totally be way off)

Assembly as I know it, is used because it's not resource heavy if written properly. And an antivirus definitely needs to be written properly.

Anyways. Yeah, I am probably going to give it a look for use on my intel workstation/server. It's definitely one of the 'vulnerable' chips they released.

Oh well. So long as it does its job.

Symantec. shudders with rage