I’m not sure people who aren’t network administrators should be putting public IPv6 all over their LAN behind their router, at least not until v6 is more common and routers have better inbound security features for such things (like how NAT functions today for v4).
Every single tutorial on the topic is IPv4-specific and until IPv6 isn't more common, people will not write guides and tutorials with IPv6 in mind. So until the knowledge of proper security on open networks is common enough among home tinkerers, we should not be recommending people just throw everything straight onto the open Internet.
somewhat simplified like this using iptables on linux:
iptables -t nat -A POSTROUTING -o WAN -j MASQUERADE
vs iptables -A FORWARD -i WAN -m state ! --state RELATED,ESTABLISHED -j REJECTThere's nothing wrong in using NAT to increase the cost of attack as a part of a larger defence strategy.