You should use applications you need to protect your data traffic. And only this data. Never use HTTPS for data that does not need to be protected since there is an extra cost to manipulate this data.
But understand that a lot needs to be protected. Remember that data can be manipulated in the middle of the path. HTTPS helps prevent them from being altered in this process without even being detected. So I'm not just talking about passwords or credit card numbers. Any information that is unacceptable that can be intercepted should be protected, even some that seem trivial. Imagine an address changed and delivery goes the wrong place. Even a simple age can make you display inappropriate content for people who can not access it. The examples can be numerous.
HTTP is a protocol for transporting data typically between browsers and servers. Most of the things you do for web uses HTTP. And HTTPS is just a "safe" way to traffic that data. As you have already read in the other question the data is trafficked encrypted.
Whenever someone does a login on a site , it should be encrypted so the password entered is not easily read if the data packets are unduly caught. Then you should use HTTPS.
If there are other data that should be protected, even if only to protect the privacy of those involved, it should use HTTPS.
All browsers and HTTP servers like Apache and IIS know how to handle this data traffic encrypted by the HTTPS protocol.
But this is not enough, you need a certificate installed on the server to use the protocol correctly. This certificate must be purchased ( free options with limitations) in a in English ) that is recognized at least in the most used versions of browsers since they must also have a certificate to establish the communication. These details are already in the other question.
Of course, for internal things, you can generate your own certificate. It can be used for everything, but it will not be considered reliable outside of its internal use, which also needs to be configured to accept its own certificate.
The language itself does not necessarily have to know how to handle the protocol. At least not to do trivial things. Of course in some situations you may want to know how to handle the protocol directly. But in general you just need to determine which protocol to use indicating HTTPS. So you do not need to deeply understand how the protocol works to do the basics, you just have to have your server configured correctly with a valid certificate.
Remember that if the page is HTTPS. All your content should be too.
Overall this is it, of course there are some simplifications there. If you have more specific questions, post more specific questions.