This is a dishonest characterization of how every smart speaker in existence works. There is no continuous stream as this statement implies.

There is a continuous buffer of a couple of seconds for the device to locally catch a wake word. (You can verify this by disabling the device's internet connectivity - it will still catch the wake word and speak an apologetic message about not being able to connect). Also, changing the wake word requires a full restart, which says "firmware" to me.

After the wake word is spoken, that buffer and anything immediately after it is what gets sent up to the cloud for voice recognition.

The buffer serves a purpose in that it prevents an awkward pause between the wake word and the action reqeusted. (So you get to do "Alexa, turn on the lights" rather than "Alexa? bong Turn on the lights.")

The "user hostility" and "gimmick"-ness of this design is entirely subjective and quite overblown, in that "nobody will ever use Dropbox when they could just use rsync and a cronjob"-type bias that HN tends to have.

I'd say it beats the alternative from a pure functionality standpoint.