the main advantage for me is that Cloudflare's free tier has no bandwidth limit. Netlify's free tier has a 100GB/month limit (https://www.netlify.com/blog/2019/02/26/netlify-and-bandwidt...). I put Cloudflare in front of my Netlify site because of that.
Ah, you know for some reason I was thinking Cloudflare was also doing some hosting, and now I realize I shouldn't make comments on things without having consumed a coffee to start the day.
I also have Cloudflare in front of my site, but that was there before I made the switch, and it's great!
I used about 350GB in the last month according to Cloudflare (over about 3.5 million requests), probably because I serve a lot of 5-10MB PDFs. Being able to not worry about bandwidth fees for a medium sized personal site is really amazing.
Or instead spend some time to optimize your website a little (like not hosting yourself standard stuff like jquery, Bootstrap and such, compress images, etc). So you can serve 10s of 1000s visitors without hitting a 100 GB free tier ;-)
You're responding to someone running one of the more well-known developer blogs and hosting PDFs, it's not exactly surprising she might need a bit more bandwidth.
That does not follow, though. It's not like people are generally optimizing their bundle sizes when they are in services where that costs money like AWS or there's a quota like Netlify.
Not having a limit liberates you to deliver other types of content and you have something less to worry about. It does not imply not worrying about optimizing your users' experience
I also have Cloudflare in front of my site, but that was there before I made the switch, and it's great!