Isn’t anyone more than me concerned about the enormous amount of energy the WEB transforms?
I feel very frustrated. This post is wild, unpolite and unstructured but I hope someone will pick up the message.
Outdated HTML ?
Even though much effort is spent on virtualization WEB-serves the overall load is depending on the fact that we feed the computers with data using OUTDATED protocols.
a mess of construction like using LEGO, MECCANO and bunch of different glues at the same time
I mean that the HTML really is mature enough for architectural refactoring.
Most of you – I think – are often disturbed by long response time but also quite annoyed on uncertain behavior of a WEB interaction. The very point in this observation is that the basic HTML with its PAGE/BODY metaphor is from old batch -90 IT-system. In a session – constituted by a set of interactions – the whole content on the user screen is (re)produced by the server, transported and rendered.
Even though most of the visual screen is he same! My experiences the last years are that 90% of the visual screen is the same between two steps – just 10% is changed.
But HTML is not able – by design – to just send the changes.
But the basic HTML has no tag for <ReplaceSomething ID=”…>.
If such a mechanism – REPLACE – was introduced I think we can reduce the energy utilization by 90% – a magnitude – and also make it much more easier for the Dialog Constructor on the server to really make a radically more understandable interactions and express the in basic HTML perhaps using the MVC Pattern.
The WEB-browser must deal with the <REPLACE>
Introduce a <!doctype ResponseCouldBeBodyOrReplace …/> telling that responses from an HREF et al. request might be one of
1. <!doctype as present standard of course …>
2. <!doctype ResponseCouldBeBodyOrReplace …/>
3. <!doctype Replace…/><REPLACEPARTS>…</REPLACEPARTS>
Focus on goals (Energy Utilization)
Forget the obsessed focus on functions and performance!
Forget cache (rethink).
Recfactor CSS into layout (positioning) and style (texture) at least.
Forget for the present.
Hurry up before the goverments detects that there are no relationships between W3C and Energy Utilization.
I’m not the guy to run or orchestra a group on ‘WEB Protocols and Energy Utilization’ but I can contribute with experience and idea and reviews.