Speaking as an information security professional, it is a damn good idea to implement SSL/TLS on any login field. That said, as (mostly) technical people here

Speaking as an information security professional, it is a damn good idea to implement SSL/TLS on any login field. That said, as (mostly) technical people here at HN, we should realize that putting our machines in a position where traffic could be sniffed or altered--that is, on the same public WiFi or subnet as a malicious user--is risky to begin with. DNS and ARP poisoning could redirect any HTTP requests to anywhere else on the Internet whether or not it's trying to initiate an encrypted connection. SSL is an important aspect of security, but can't be relied upon to protect you in a hostile environment.