[roelschroeven]

> > Won't this get flagged by anti-virus scanners as suspicious?

> Unfortunately, yes. We consider this a problem for the anti-virus scanners to solve.

I don't think the anti-virus scanners consider Zig important enough, or even know about. They will not be the ones experiencing problems. Having executables quarantined and similar problems will fall on Zig developers and users of their software. That seems like a major drawback for using Zig.

[dleslie]

Yup. This sentiment expresses quite clearly how Zig has no significant understanding or interest in being a language used for widely distributed applications, like video games.

There's no way I can ship a binary that flags the scanners. This wouldn't be the first language I've avoided because it has this unfortunate behaviour.

And expecting virus scanner developers to relax their rules for Zig is a bit arrogant. Some virus scanners started flagging software built with Nim simply because Nim became popular with virus authors as a means to thwart scanners!

[monocasa]

Yeah, I had this problem when shipping go binaries on Windows. Antivirus vendors really do not care that your program regularly shows up as a false positive due to their crappy heuristics, even if you have millions of users.

[accoil]

It's a common enough issue with go that they wrote a faq on it too: https://go.dev/doc/faq#virus

[anfragment]

Have you tried code-signing with an EV certificate? If so, did it help? Asking for a friend.

[slopinthebag]

>> Unfortunately, yes. We consider this a problem for the anti-virus scanners to solve.

In reality it will be a problem for the developers to solve, and the solution will be to use a different language lol

[josephcsible]

Antivirus is going to flag you no matter what if you're not a big-name developer with an expensive certificate. Even a "hello world" GUI program done with MSVC and Win32 gets called the Wacatac Trojan without one. We shouldn't let their incompetence dictate how our software works.