Very interesting. This sounds like a response to the Mighty [0] launch which Paul Graham has been defending on twitter recently after an outcry from some of the 'hardcore' developers such as Jonathan Blow [1] and Casey [2]. [0] https://www.mightyapp.com/ [1] https://twitter.com/Jonathan_Blow/status/1387101172230672389 [2] https://twitter.com/cmuratori/status/1387645578067124224
It is fascinating to me how quickly people reject the premise of Mighty, even after PG lists all the good reasons for replacing judgment with curiosity. I’ll admit, my initial reaction to Mighty was “I can’t imagine it ever being faster than my behemoth PC.” But then I stopped for a second and got curious. What is Mighty, really? It is a thin-client. That’s it. And are thin-clients a bad thing? Well, if latency is an…
Because thick client distribute the load among many computer. With a thin client all that load is way more centralised.
> I would never attempt to train a PyTorch
No one is asking you to do that. We're talking about Mighty, a thin client that:
- runs a beefy VM in the cloud
- runs a single app, Chrome, in that VM
- streams video to the client
If a million people run Chrome on their laptops and keep it open for the entire day (and your browser is usually open throughout the day), that's... just a million people with their laptops.
If a million people run Chrome through Mighty, Mighty needs a million VMs always open, and a million video streams, also always open.
See how a thick client is better than a thin client?