Not really-- this solution is even weirder. We've already been moving toward a "thin client" solution with everything running in web browsers, which actually runs a web application on the server. That's already a push toward the "thin client" model.
This then takes that and runs the browser on the sever, and streams the output locally. So it's like saying, "What if we emulate the thing client on the server too, and try to make a thinner client that just connects to the emulated thin client, which then connects to the server to run things."
If web browsers are such resource hogs that you can't even run the browser on your local computer, it's time to reevaluate what you're doing.
Living on Earth may be expensive, but it includes an annual free trip around the Sun.