it’s frustrating because webpages were really functional without this problem a decade ago. i don’t know why links jump around today. is it because it’s cheaper to let the client figure out what content they need instead of using server-side computation?
Because frontend webdevelopers use some very large framework to make things “look nicer” and don’t care about resource optimisation? They do the opposite just for some silly colouring effect, shade etc. The old ugly stuff was a lot smaller and quicker to load.
yeah, no, im with you on that point where frontend developers don’t care. but why did that framework catch on in the first place? we used to use php where the server would grab all the data relevant to your account and convert it into one html page. but now it seems the user’s laptop is tasked with pulling each element of their own website. maybe it’s easier to scale? like you can have the user’s data split across different servers and not require any communication between servers on the backend?
it’s frustrating because webpages were really functional without this problem a decade ago. i don’t know why links jump around today. is it because it’s cheaper to let the client figure out what content they need instead of using server-side computation?
Because frontend webdevelopers use some very large framework to make things “look nicer” and don’t care about resource optimisation? They do the opposite just for some silly colouring effect, shade etc. The old ugly stuff was a lot smaller and quicker to load.
yeah, no, im with you on that point where frontend developers don’t care. but why did that framework catch on in the first place? we used to use php where the server would grab all the data relevant to your account and convert it into one html page. but now it seems the user’s laptop is tasked with pulling each element of their own website. maybe it’s easier to scale? like you can have the user’s data split across different servers and not require any communication between servers on the backend?