Are you saying that the default firewall setting for LAN to WAN traffic is recommended to be set to deny? That is an administration nightmare. Block all inbound from the untrusted network (WAN > LAN), allow all outbound from the trusted network (LAN > WAN), add specific rules to allow inbound connections such as vpn and add specific rules to block outbound connections such as hosts restricted from accessing WAN. Having to write specific rules to allow outbound traffic through a firewall when there are so many services running on systems that require access, such as update services, seems insane.
In regards to the article, which was written in 2005, the writer is criticizing the policy of default allow on a WAN > LAN connection, or a default allow on system execution (allowing any executable to run just because a user clicked on it).
Point is, if you trust it, allow it, and if you don't trust it, don't allow it, but don't make your job harder.