3 ms·
> Making the whole thing client side also let him scale from a small handful of users to literally millions with basically zero additional work. But everyone o
by com2kid 5y ago
> Making the whole thing client side also let him scale from a small handful of users to literally millions with basically zero additional work.
But everyone on HN is telling me that I should move away from client side and render everything server side! In fact, all state should be server side! Use a fancy library that opens a web socket and turn the users 4+core computer into a mindless zombie controlled by a .25CPU VM somewhere.
/s
- yen223 5y agoI don't know how Wordle managed to scale to 3 million players without Kubernetes, it must be magic.
- com2kid 5y agoWhen people ask me why I like SPAs: Because web servers are really good at serving up static files. That is it. I get to make an app, deliver it through the web, and not worry about server resources. I do have to worry about making the app not suck, but as a software engineer I should always be worrying about that! Web, mobile, desktop, making code not a bloated mess is kind of important no matter where it is running.
- mmcnl 5y agoYou're dumping all the compute requirements onto the client. But that's not always a bad thing. When done good, it's pretty good. Prime example: Worldle. No need to hate frontend.