{"id":25075839,"user":"Aperocky","time":1605219083,"time_ago":"5 years ago","type":"comment","content":"

wait what, how?","comments":[{"id":25075862,"user":"szhu","time":1605219196,"time_ago":"5 years ago","type":"comment","content":"

https://news.ycombinator.com/item?id=23281564","comments":[{"id":25076479,"user":"jrochkind1","time":1605222319,"time_ago":"5 years ago","type":"comment","content":"

The behavior documented there is on FIRST run of a new executable.

You can like that behavior or find it unacceptable, but the issue in OP is not that, it was applying to executables that had already been launched plenty of times on the machine.","comments":[{"id":25082625,"user":"SolarUpNote","time":1605278488,"time_ago":"5 years ago","type":"comment","content":"

[deleted]","comments":[{"id":25082729,"user":"jrochkind1","time":1605278920,"time_ago":"5 years ago","type":"comment","content":"

Right. The recent problem (in top-level OP, and that you were presumably experiencing) was not just first run, but the behavior explained at the GP link (https://news.ycombinator.com/item?id=23281564 , HN thread for https://lapcatsoftware.com/articles/catalina-executables.htm...) is just about first-run, so the behavior explained at the GP link is not sufficient explanation for the recent problem, it's not talking about the same thing.","comments":[],"comments_count":0,"level":3,"url":"item?id=25082729"}],"comments_count":1,"level":2,"url":"item?id=25082625"}],"comments_count":2,"level":1,"url":"item?id=25076479"}],"comments_count":3,"level":0,"url":"item?id=25075862"}],"comments_count":4,"url":"item?id=25075839"}

Comment by Aperocky