machomaster
Joined 5 years ago
Joined 5 years ago
2. Let'a move some of the compute to the clients, so they can pay for it.
3. Oh, we are moving more and more JS to clients, it gets complex. Let's make big JS frameworks to help contain this complexity.
4. This is a shit-show, Frameworks cause all kinds of problems with developing, deployment, fixing, latency, instability, etc.
5. Let's optimize everything by caching on server and sending to the client ready html content! Arrived exactly where they started from.
What's the point of having a fast web site, if your choice of font sizes makes the content unreadable (or at least requiring effort, and straining the eye-sight and aggravating the reader)!..
Released this year. Homm3 mechanics, aesthetic close to Homm2.
Yeah, there are people who think that they are being paid to be at work, not to do work, to apply themselves, to engage, to provide and produce. And it sucks to work with those kinds of people.
Don't be silly.
Perhaps this is where the core problem lies. Have you considered, that this obsession to leave servers and to try to unload all the work to the clients is the wrong way (for most sites)?