I have to remind everyone that changing a database to the SIMPLE Recovery Model is one of the very worst things you can do if Point-In-Time Backups are in effect and, except for staging/temp user databases, such backups should generally in place.
Switching a database from FULL to SIMPLE breaks the logchain. It can be restarted only by having a good full backup and taking a DIF or by taking another full backup.
Minimally logged operations can be had in the BULK LOGGED Recovery Model without breaking the logchain. There is a caveat, though. Any logfile backup that contains a minimally logged operation must either be used in its entirety or not used at all during a restore. Obviously, both can interfere with a Point-in-Time restore.
I also have to remind everyone that while some of these tricks will sometimes help certain types of code, they usually have very little impact compared to writing the code correctly. Some of these tricks might make a piece of code run 50 to 100% quicker. Writing the code correctly can actually make the code tens to thousands of times quicker and more resource efficient.
There's no question that these tricks and good hardware are a bit important but if you want real performance, that's in the code itself. Likewise, it doesn't matter how many of these tricks you pull off or how good your hardware is, bad code can still cripple your server.