←back to thread

The Rise of Hybrid PHP: Blending PHP with Go and Rust

(yekdeveloper.com)
133 points avan1 | 1 comments | 30 Aug 25 19:02 UTC | HN request time: 0s | source
Show context
osigurdson ◴[30 Aug 25 22:16 UTC] No.45078470[source]▶
Sometimes I think we should go back to basics: pixels, data, latency / bandwidth. The web is an optimization problem in the sense that we want to render correct pixels at perceptual speed given latency and bandwidth constraints.

It should be more like: what pixels is the user about to see? What data is need to set the the pixels? What data is likely needed next and optimistically pre-fetch - something like that.

replies(3): >>45078683 #>>45078991 #>>45080169 #
singinwhale ◴[30 Aug 25 22:51 UTC] No.45078683[source]▶
Thinking about user seeing pixels is seeing just a part of the picture. As all software projects you don't optimize just for immediate user experience but also development time. Time to first draw rarely coincides with development time.
replies(2): >>45078810 #>>45079902 #
1. osigurdson ◴[31 Aug 25 02:46 UTC] No.45079902[source]▶
Dealing with over-fetch / under-fetch most certainly does chew up development time. Creating endless api endpoints that are only used by the web UI is also very time consuming (the industry is finally recognizing how dumb this is and moving back to older SSR approaches). How about, "the user is allowed to access this information on the server - system you figure out what / when to fetch portions of this information for viewing"?