Subj : HTTP 2: whole lot of bloat bundled with more bloat
To   : Arelor
From : August Abolins
Date : Fri Sep 10 2021 08:10:00

Hello Arelor!

** On Friday 10.09.21 - 03:52, Arelor wrote to August Abolins:

 A> The "Web" would be WWW.

[...]

Noted! Thx.

 A> In this context, it means applications served over http(s),
 A> websockets and other web browser's technology, specially
 A> when they are served from mainstream platforms.

 A> I don't know if you are up-to-date with http standards, but
 A> the http specification is scattered across 6 RFCs (think of
 A> them as reference documents) or so. [...]

6 RFCs.  That's incredible.  That reminds me of my MIL-STD  
(MIL-SPEC) days, where one standard referred to another  
standard as it incorporated the next standard, and so on.


 A> HTTP is not getting better. It was a protocol designed for
 A> serving documents but big tech wants it to serve
 A> applications [...]

 A> [...] HTTP 2's main selling point is precisely that they
 A> can ship a whole lot of bloat bundled with more bloat in
 A> the same connection.

Well.. the folks behind the development of the standard seem to  
have been convinced that it *was* a good thing.  Maybe someone  
was pretty good at twisting arms.


 A> Compare that to the reference document for something like
 A> Gopher, which can be understood in a matter of minutes.

Gopher seems to be very quick and efficient, but I just can't  
seem to want to use it very much.  It just seems too plain.

BTW.. the "Xibalba - Enigma Bulletin Board System" link on your  
gopher page doesn't seem to work.
--
  ../|ug

--- OpenXP 5.0.50
 * Origin: (} Pointy McPointface (618:250/1.9)

.