Fully agree, hopefully Fred can find something that reverse this trend, it is just not normal that so many PB programs get flagged there must be something in those exe that upset those AVOlby wrote:I know a few people strongly opposed the notion of fixing something that is not broken. But PB is not Microsoft or any other big player therefore we have to play according to their rules. While it is possible to tell someone to uninstall completely or use a different AV it is a futile request. I don't expect someone to buy a new AV just because "my little utility written in PB" is quarantined. They'll just find another piece of software. In my case it would be nearly impossible to accommodate PB and request the corporation to change to another AV provider or get rid of it at all (which will not happen anytime soon since AVs usually come bundled with firewalls, networks threat prevention, safe web browsing etc). The answer would be simple, why are you using PB, just switch to something else that doesn't require any extra work. Sadly this doesn't help to promote PB outside bedroom and hobbyist coder scene.
TLDR;
If the mountain will not come to Muhammad, then Muhammad must go to the mountain. Therefore the best course of action in my opinion would be to try changing the binary code generated by PB compiler to something that will cause less false-positives by, perhaps, working together with AV developers such as Symantec.
We love PB and invested a lot of time in it, but by the end of day if it cant be used to sell/share programs then what's the point and we need to move into something else even if we have to restart from scratch What happened with marc_256 is really sad and the PB source code cannot be used anywhere else
To be honest, i am in the same boat as you and for the past 2 years i have been delaying this moment of truth, but seemingly things are not going to change any time soon ... so most likely i will have to walk away as well, probably others have already done it silently ?!