Correction - you
think you don't need it when you're reading those things, which indicates a serious misunderstanding of HTTPS' problem domain.
Unless what you're trying to say is that you're totally fine with third parties (governments, ISPs, the person whose WiFi you're connected to, some random script kiddie):
- snooping on your browsing habits (you can intercept and read off an entire HTTP request plain as day, including headers such as User-Agent strings, the specific URL that's being visited, etc, allowing you to build a profile of/digitally fingerprint the unsuspecting user; these are encrypted in an HTTPS request)
- maliciously handling your requests, returning whatever response they please instead of forwarding it to the intended remote, allowing them to not just censor the content but straight-up lie to you without your knowledge
- tampering with responses - injecting a cryptominer, tracker, script that adds your computer to a botnet or other malicious/non-benevolent script into the response before it reaches you or even just fucking around with the CSS or throwing in porn for the lulz