Then it should not be compared to adblock.

I don't follow this logic. Both do generally the same thing, but with different approaches. This to me would make a comparison of the two different approaches very valid.

That is not what is happening in the post. Only the filtering/element-hiding capabilities of both are being compared.

That is exactly what is happening in the headline, however.

You are calling HTTPSB an alternative for Adblock Plus.

One of the major use cases of Adblock Plus is effectively "Fire and Forget" mode - enable it and then don't worry about it.

You are saying HTTPSB does not support this use case.

As such, I don't see why you can call it an alternative to Adblock Plus.

It is an alternative. to all of like 1000 people worldwide who are willing to figure it out. So basically fire-and-forget mode, or broke.

That's like saying that walking isn't an alternative to driving because there's no wheels. It's different, has a superset of functionality, and a different interface. It isn't a fork of ABP.

It does not have a superset of functionality.

Adblock Plus / Edge has a "Fire and Forget" mode, as I described in my grandparent comment. HTTPSB does not. Hence, HTTPSB's functionality is not a superset of Adblock Plus/Edge's functionality.

Your analogy fails too. I use a manual javascript blocking add-on (noscript) instead of an automatic blacklisting one and its not a deal-breaker. Minor effort required.