SSL/TLS doesn't solve this problem noted by GP:

Furthermore, and most importantly, by using SSL/TLS, the data being sent by the browser to the server is encrypted as it passes through the network, but however remains readable by the server when it reaches it. Whereas with client-side JS crypto, the server cannot read the sensitive data.

This is a shortcoming in the argument made in the article, because it wrongly assumes that we would always want the server to decrypt our data.

I am not saying JS does solve this, but SSL doesn't, and it isn't even meant for that use case.